Skip to main content
Glama

save_booking_product

DestructiveIdempotent

Create or edit a booking package or membership. Include its ID to edit or set active to false to retire it. Reuse the same idempotency key on retry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "save_booking_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare idempotentHint=true and destructiveHint=true, so the bar is lower, and the description still adds real value: 'set active to false to retire it' tells the agent the destructive path is a soft deactivate rather than a hard delete, and 'reuse the same idempotency key on retry' gives actionable retry behavior. It does not cover side effects on already-sold packages or existing bookings referencing the product.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the create/edit decision, then the retire path, then the retry rule. No filler, no restatement of the tool name, and each sentence carries a distinct operational instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating tool with destructiveHint=true and no output schema, the definition covers the core flow adequately but leaves gaps an agent would want: permissions or validity requirements for creating a membership, whether edits to price/credits affect in-flight purchases, and what identifier the call returns. Given the nested product object with nullable credits and validDays, the definition is serviceable but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema is a nested product object with roughly nine fields, so the description must carry the load. It partially does: it supplies the meaning of id (present = edit), active (false = retire) and idempotencyKey (stable across retries), all rules the schema does not encode. However, it says nothing about the business semantics of kind, credits (nullable), validDays, or price bounds, which are the fields most likely to be set incorrectly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb pair plus a well-scoped resource: 'Create or edit a booking package or membership'. The word 'booking' plus 'package or membership' distinguishes it from save_store_product without naming a sibling, so an agent can route correctly, though no explicit sibling contrast is offered.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It resolves the create-vs-edit ambiguity directly: include the ID to edit, omit it to create, and set active to false to retire. That is concrete operational guidance. What is missing is guidance on when to use this versus list_booking_products or save_store_product, and no preconditions (e.g., plan/permission limits) are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources