Skip to main content
Glama

Assign booking guide

assign_booking_guide
Destructive

Assign or reassign the guide who will run a booking. Get guide_id from the guides list on get_business_overview.

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": {
      "booking_id": "<booking_id>",
      "guide_id": "<guide_id>"
    },
    "name": "assign_booking_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
guide_idYesThe id of a guide on this business, from get_business_overview.
booking_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=true; the description's "reassign" wording is consistent with the destructive hint, since an existing guide is replaced. It does not disclose side effects an agent would want before a destructive mutation — whether the prior guide or client is notified, or whether the change is reversible. No contradiction with annotations.

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

Conciseness4/5

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

Two short sentences, with the action front-loaded and the data-source hint second. The second sentence largely restates the guide_id schema description, so it is mildly redundant rather than wasteful.

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?

Given a destructive mutation with no output schema, the definition leaves out what a successful call returns (updated booking vs. bare confirmation) and what side effects accompany reassignment. Annotations carry the safety signal, so this is adequate but with clear gaps.

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 coverage is 67%, with guide_id and business_id already described in the schema, including the same get_business_overview pointer the description repeats. booking_id has no schema description and the description likewise adds nothing about its meaning. Baseline 3 is appropriate given the schema does most of the work.

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?

States a specific verb pair ("assign or reassign") plus the resource (the guide who will run a booking), so the operation is unambiguous. It doesn't distinguish itself from any sibling by name — get_business_overview is cited as a data source, not as an alternative — but the purpose itself is clear.

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

Usage Guidelines3/5

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

The phrase "assign or reassign" usefully signals both first-time assignment and replacing an existing guide, and it tells the agent where to source guide_id. There is no guidance on preconditions (e.g., must the booking be in a pending state?), no exclusions, and no mention of what happens to the previously assigned guide.

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