Skip to main content
Glama

Cancel the call or visit.

cancel_appointment

Cancel the call or visit. The mover is told. The customer can book again. Scope: jobs:write.

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": {
      "job_id": "<job_id>"
    },
    "name": "cancel_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id (ULID)
reasonNoOptional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: the mover is notified, the customer can rebook, and the required scope is jobs:write. It does not explain error behavior or whether the cancellation is reversible beyond the rebooking hint, but it gives solid side-effect and authorization context for a simple mutation.

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?

The definition is short and front-loaded with the action, followed by side effects and scope. Every sentence adds useful information, with no redundant explanation or filler.

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

Completeness4/5

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

For a two-parameter cancellation tool with no output schema, the description covers purpose, notification behavior, rebooking outcome, and auth scope. It could be enriched with response or error details, but it is sufficient for correct invocation.

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 job_id and reason are already documented in the input schema. The description does not add syntax, format, or selection meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: cancel the call or visit. This clearly identifies the operation and distinguishes it from request/accept/list-style appointment siblings, though it does not explicitly name an alternative tool.

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?

Use is implied by the direct instruction to cancel and by the outcome that the customer can book again. However, there is no explicit when-to-use guidance, no stated exclusions, and no comparison to sibling appointment tools.

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