Skip to main content
Glama

remove_appointment_payment

DestructiveIdempotent

Remove an incorrectly recorded manual appointment payment from the ledger by payment ID.

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": {
      "paymentId": "<paymentId>"
    },
    "name": "remove_appointment_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds the useful scoping detail that it targets manual appointment payments 'from the ledger', but says nothing about reversibility, audit trail, or what happens to any linked invoice/appointment balance.

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?

One sentence, front-loaded with the verb and scoped resource, with zero filler. Nothing could be trimmed without losing signal.

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, non-read-only mutation with no output schema, the definition is adequate but thin: it does not state whether the removal is reversible, what confirmation or permissions are needed, or what the caller gets back. An agent can call it, but not predict consequences beyond the annotations.

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

Parameters4/5

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

The single parameter is self-explanatory (`paymentId`, UUID with pattern) and the description explicitly frames it as the payment's identifier, confirming it selects the record to remove rather than, say, an appointment. With one obvious parameter, that is sufficient added meaning.

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 ('Remove') plus a precisely qualified resource ('incorrectly recorded manual appointment payment') and the identifier ('by payment ID'), which separates it from record_appointment_payment and remove_invoice_payment. It stops short of explicitly naming the sibling it contrasts with, so a 4 rather than a 5.

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?

'incorrectly recorded' implies the intended condition (correcting a mistake rather than routine cleanup), but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for other payment-removal cases. Usage must be inferred from the qualifier.

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