Skip to main content
Glama

get_appointment_payments

Read-onlyIdempotent

Read the payment ledger and outstanding balance for an appointment. Amounts are in minor units.

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>"
    },
    "name": "get_appointment_payments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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 readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact beyond that: amounts are returned in minor units. It says nothing about pagination, currency, ordering, or what happens when an appointment has no payments.

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?

Two short sentences with zero filler, front-loaded with the resource and followed by the one non-obvious data-format caveat. Nothing could be removed without losing information.

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?

With no output schema, the description carries the return-shape burden and does name the two things returned (ledger and outstanding balance) plus the unit convention. Residual gaps (currency handling, whether individual payment records or only aggregates are included, behavior for unpaid appointments) are minor for a single-parameter read tool.

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 0%, so the description must compensate, and it only does so implicitly: 'for an appointment' lets the agent infer that the single required 'id' is an appointment UUID. It does not state the identifier type explicitly or say where to obtain it, leaving the schema's format/pattern as the only signal.

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 ('Read') and a specific resource pair ('payment ledger and outstanding balance') scoped to one appointment. An agent can tell it fetches payments for a single appointment, but nothing in the text distinguishes it from the sibling list_appointment_payments or explains why one would pick this over that.

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?

Usage is only implied: the phrase 'for an appointment' suggests a single-appointment lookup versus a listing call, and the request for ledger plus balance suggests a reconciliation/checkout use case. There is no explicit when-to-use statement, no exclusion, and no named alternative such as list_appointment_payments.

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