Skip to main content
Glama

mark_appointment_no_show

Destructive

Record a no-show for an ended appointment. Read its current revision and agreed fee first. This can retain a prepaid fee, refund the remainder, or charge a saved card. Confirm the policy and fee before calling.

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": {
      "id": "<id>",
      "revision": "<revision>",
      "expectedFee": "<expectedFee>",
      "acceptPolicy": "<acceptPolicy>"
    },
    "name": "mark_appointment_no_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes
expectedFeeYes
acceptPolicyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already flag this as destructive, non-idempotent and open-world, so the description's job is to say what actually gets destroyed. It does that well: the call can retain a prepaid fee, refund the remainder, or charge a saved card, which is real financial-consequence disclosure rather than restatement. It does not state whether the action can be undone or what an error response looks like, keeping it below a 5.

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?

Four short sentences, front-loaded with the action, then prerequisites, then consequences, then the confirmation checkpoint. Nothing is redundant, though the closing 'Confirm the policy and fee before calling' partly repeats the earlier 'Read... agreed fee first'.

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 destructive, financially consequential mutation with four undocumented parameters and no output schema, the description covers purpose, preconditions and consequences but is silent on mismatch/conflict behavior and on what the caller receives back. Adequate to avoid misuse, not fully 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 coverage is 0%, so the description must carry parameter meaning, and it partially does: 'current revision' conveys that revision is an optimistic-concurrency token that must match, and 'agreed fee' clarifies that expectedFee is the caller's asserted fee, likely used as a guard. It leaves acceptPolicy unexplained beyond 'confirm the policy' and says nothing about what happens on a revision or fee mismatch.

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?

The description names a specific verb and resource ('Record a no-show') and adds a scope qualifier ('for an ended appointment') that separates it from siblings such as cancel_appointment or complete_appointment. An agent can identify the operation without opening the schema.

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 gives concrete pre-call guidance: read the current revision and agreed fee first, and confirm the policy and fee before calling. It stops short of naming an alternative tool (for example cancelling or rescheduling instead of a no-show), so the routing guidance is contextual rather than explicit.

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