Skip to main content
Glama

Change the time

change_booking_time
Idempotent

Move a booking to another open time (find_open_times with the booking's job). Free until 24 hours before; it goes back to Ryan to confirm.

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": {
      "link": "<link>",
      "start_time": "<start_time>"
    },
    "name": "change_booking_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe private change-or-cancel link from the customer's confirmation email (or from request_booking).
start_timeYesA start_time exactly as find_open_times returned it (ISO 8601, UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare write, non-destructive, idempotent behavior; the description adds the genuinely useful operational constraint that changes are automatic until 24 hours before the appointment and after that require human confirmation. That extra context is valuable, but "Free" is ambiguous (no fee versus freely allowed) and "it goes back to Ryan to confirm" leaves unclear whether the call succeeds with a pending status or fails outright.

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

Conciseness3/5

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

The definition is short and front-loads the action, which is good, but the second clause is compressed to the point of ambiguity – an unglossed human name and an undefined "Free" force the reader to guess. Every sentence should earn its place, and this one spends its brevity on unexplained shorthand rather than clarity.

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?

With no output schema, the description carries the burden of explaining what the agent gets back, and it only partially does so – it never says whether the response confirms the new time, returns a pending-confirmation state, or reports the 24-hour cutoff as an error. The precondition workflow is covered, but the post-call outcome is not.

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 100%, so both parameters (link and start_time) are already fully documented, including the ISO 8601/UTC requirement and the source of the link. The description adds only the provenance tie between start_time and find_open_times output, which is marginal beyond the schema baseline.

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

Purpose5/5

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

"Move a booking to another open time" names a specific verb (move) and resource (booking), and the parenthetical routes the agent to find_open_times as the source of a valid target, which distinguishes this from cancel_booking and get_booking in the sibling list.

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?

The description prescribes the correct prerequisite (call find_open_times with the booking's job, then use one of its results), which is real when-to-use guidance. It stops short of stating when NOT to use it or what the agent should do if the request falls inside the 24-hour window, so the caller must infer the escalation path.

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