@anuma/sdk 6.28.1 → 6.29.0

package/dist/expo/index.cjs

@@ -6282,26 +6282,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -6441,6 +6475,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/expo/index.mjs

@@ -4680,26 +4680,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -4839,6 +4873,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/index.cjs

@@ -2261,20 +2261,51 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 function applyToolSets(matchedNames, availableNames, scores, toolSets = BUILT_IN_TOOL_SETS, independentThreshold = 0.65) {
@@ -2434,6 +2465,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/index.mjs

@@ -2055,20 +2055,51 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 function applyToolSets(matchedNames, availableNames, scores, toolSets = BUILT_IN_TOOL_SETS, independentThreshold = 0.65) {
@@ -2228,6 +2259,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/react/index.cjs

@@ -6671,26 +6671,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -6830,6 +6864,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/react/index.mjs

@@ -4809,26 +4809,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -4968,6 +5002,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/server/index.cjs

@@ -33290,26 +33290,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -33449,6 +33483,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/server/index.mjs

@@ -31554,26 +31554,60 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 var CONFIRMED_ACTION_TOOL_SETS = /* @__PURE__ */ new Map([
-  ["book_restaurant", "restaurant-booking"],
-  ["anuma_book_restaurant", "restaurant-booking"],
-  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-booking"]
+  ["book_restaurant", "restaurant-book"],
+  ["anuma_book_restaurant", "restaurant-book"],
+  ["anumapaymentsmcp-anuma_book_restaurant", "restaurant-book"],
+  ["cancel_reservation", "restaurant-cancel"],
+  ["anuma_cancel_reservation", "restaurant-cancel"],
+  ["anumapaymentsmcp-anuma_cancel_reservation", "restaurant-cancel"]
 ]);
 function expandToolSetsAdditive(matchedNames, availableNames, scores, toolSets, activeSetNames) {
   const result = new Set(matchedNames);
@@ -31713,6 +31747,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/tools/index.cjs

@@ -847,7 +847,7 @@ var CONFIRM_TOOL_NAME = "prompt_user_confirm";
 function createConfirmTool(options) {
   return createInteractiveTool(options, {
     name: CONFIRM_TOOL_NAME,
-    description: "Ask the user to approve a specific action before it happens. Use before anything that spends money or is hard to undo, such as booking a restaurant table or placing an order. List every parameter of the action, with the exact values you are about to use \u2014 the user approves what this card shows, and nothing else. Returns whether they confirmed. Do not use for ordinary yes/no questions; use prompt_user_choice for those.",
+    description: "Ask the user to approve a specific action before it happens. Use before anything that spends money or is hard to undo, such as booking or cancelling a restaurant table, or placing an order. List every parameter of the action, with the exact values you are about to use \u2014 the user approves what this card shows, and nothing else. Returns whether they confirmed. Do not use for ordinary yes/no questions; use prompt_user_choice for those.",
     parameters: {
       type: "object",
       properties: {

package/dist/tools/index.mjs

@@ -691,7 +691,7 @@ var CONFIRM_TOOL_NAME = "prompt_user_confirm";
 function createConfirmTool(options) {
   return createInteractiveTool(options, {
     name: CONFIRM_TOOL_NAME,
-    description: "Ask the user to approve a specific action before it happens. Use before anything that spends money or is hard to undo, such as booking a restaurant table or placing an order. List every parameter of the action, with the exact values you are about to use \u2014 the user approves what this card shows, and nothing else. Returns whether they confirmed. Do not use for ordinary yes/no questions; use prompt_user_choice for those.",
+    description: "Ask the user to approve a specific action before it happens. Use before anything that spends money or is hard to undo, such as booking or cancelling a restaurant table, or placing an order. List every parameter of the action, with the exact values you are about to use \u2014 the user approves what this card shows, and nothing else. Returns whether they confirmed. Do not use for ordinary yes/no questions; use prompt_user_choice for those.",
     parameters: {
       type: "object",
       properties: {

package/dist/tools/selection/index.cjs

@@ -1997,20 +1997,51 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 function applyToolSets(matchedNames, availableNames, scores, toolSets = BUILT_IN_TOOL_SETS, independentThreshold = 0.65) {
@@ -2180,6 +2211,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/dist/tools/selection/index.mjs

@@ -1875,20 +1875,51 @@ var BUILT_IN_TOOL_SETS = [
   },
   {
     // Server tools, so this set does its work through
-    // withActiveToolSetServerTools: once a restaurant tool has run, terse
-    // follow-ups ("okay", "same as before") keep the booking chain. Each tool
-    // still reaches a fresh booking request on its own description.
+    // withActiveToolSetServerTools: once any restaurant tool has run, terse
+    // follow-ups ("okay", "same as before", "cancel it") keep every restaurant
+    // tool — discovery, booking and cancelling. Each tool still reaches a fresh
+    // request on its own description.
     // Anchors are deliberately empty (like the client's Nearby set): the set
     // is only for stickiness, not a new way to activate on a prompt.
     // prompt_user_confirm is left out of members: autoFilterClientTools always
     // sends it, and as a member any unrelated confirmation would pin this set.
     name: "restaurant-booking",
+    members: [
+      "AnumaPaymentsMCP-anuma_find_restaurant",
+      "AnumaPaymentsMCP-anuma_check_restaurant_availability",
+      "AnumaPaymentsMCP-anuma_book_restaurant",
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation",
+      "AnumaPaymentsMCP-anuma_discover_restaurants"
+    ],
+    anchors: []
+  },
+  {
+    // What a confirmed booking card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS): the booking chain only, without the
+    // discovery and cancel tools that restaurant-booking keeps sticky.
+    // Anchors are empty for the same reason as restaurant-cancel below.
+    name: "restaurant-book",
     members: [
       "AnumaPaymentsMCP-anuma_find_restaurant",
       "AnumaPaymentsMCP-anuma_check_restaurant_availability",
       "AnumaPaymentsMCP-anuma_book_restaurant"
     ],
     anchors: []
+  },
+  {
+    // What a confirmed cancel card narrows the rest of the turn to (see
+    // CONFIRMED_ACTION_TOOL_SETS). Anchors are empty for the same reason as
+    // restaurant-booking: anchors here are scored against client tools only,
+    // so a server-tool anchor could never fire. The "cancel brings list"
+    // edge on a fresh prompt is restaurant-cancel-lookup in
+    // SERVER_TOOL_DEPENDENCY_SETS.
+    name: "restaurant-cancel",
+    members: [
+      "AnumaPaymentsMCP-anuma_list_reservations",
+      "AnumaPaymentsMCP-anuma_cancel_reservation"
+    ],
+    anchors: []
   }
 ];
 function applyToolSets(matchedNames, availableNames, scores, toolSets = BUILT_IN_TOOL_SETS, independentThreshold = 0.65) {
@@ -2058,6 +2089,16 @@ var SERVER_TOOL_DEPENDENCY_SETS = [
       "OpenMeteoMCP-elevation"
     ],
     anchorMinSimilarity: 0.5
+  },
+  {
+    // The cancel tool takes its resy_token and the other values only from a
+    // live anuma_list_reservations result in the same turn, never from
+    // memory, so the list tool must ride in whenever cancel is offered.
+    // Members hold only the dependency, like openmeteo-geocode.
+    name: "restaurant-cancel-lookup",
+    members: ["AnumaPaymentsMCP-anuma_list_reservations"],
+    anchors: ["AnumaPaymentsMCP-anuma_cancel_reservation"],
+    anchorMinSimilarity: 0.5
   }
 ];
 var defaultServerToolsFilter = createServerToolsFilter({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anuma/sdk",
-  "version": "6.28.1",
+  "version": "6.29.0",
   "description": "",
   "main": "./dist/index.cjs",
   "module": "./dist/index.mjs",