Skip to main content
Glama

record_appointment_payment

Idempotent

Record money already received for an appointment. Supply the amount in minor units and the date in the business time zone. An optional tip, in minor units on top of the amount, goes to the person the appointment is with. Reuse the same paymentId on retry.

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>",
      "id": "<id>",
      "amount": "<amount>",
      "method": "<method>",
      "receivedOn": "<receivedOn>"
    },
    "name": "record_appointment_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
tipNo
noteNo
amountYes
methodYes
paymentIdYes
receivedOnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tip
      Added value: +{
      +  "default": 0,
      +  "maximum": 99999999,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by naming the mechanism behind idempotency (reuse the same paymentId on retry) and by stating where the tip goes ("the person the appointment is with"), which is a side effect the annotations cannot express. It does not say what happens on a conflicting or malformed paymentId, or whether the appointment's payment state is updated.

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?

Four short sentences, front-loaded with the purpose and then moving through units, date zone, tip destination, and retry behavior. Every sentence carries information that is not available in the schema or annotations, so nothing is padding.

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 mutation with no output schema and seven parameters, an agent still cannot tell what the call returns, whether a duplicate paymentId errors or silently returns the prior payment, or which entity `id` refers to. The unit/timezone conventions and idempotency key are covered; the identity of the target record and the failure semantics are 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 0%, so the description must carry parameter meaning. It does this well for amount and tip (minor units, tip is on top of amount), receivedOn (date in the business time zone) and paymentId (retry key). However, it never explains what `id` identifies (the appointment, presumably) or what `note` is for, leaving two of seven parameters entirely undocumented in both places.

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?

"Record money already received for an appointment" gives a specific verb (record), an explicit resource (payment for an appointment), and a scope qualifier (money already received, i.e. not a charge or a refund). That scope phrase cleanly separates it from record_invoice_payment and from the remove_* siblings without naming them.

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?

"Money already received" establishes the precondition for calling it, and the retry instruction tells the agent how to behave on failure. It stops short of explicitly naming alternatives (e.g. use record_invoice_payment for invoices, remove_appointment_payment to reverse), so routing still requires the sibling names rather than the description.

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