Skip to main content
Glama

Get a payment

get_payment
Read-only

Read a single payment by ID to retrieve status, amounts, expiry, and late-payment details for KHQR transaction checks; use webhooks for follow-up instead of polling.

Instructions

Reads one payment by its id: status (pending, scanned, paid, expired or failed), amounts, expiry, and whether it was paid late. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.

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_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe payment's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover read-only and open-world, so the description's disclosure of a metered cost ('counts toward the account's daily read allowance') and the anti-polling/webhook guidance adds substantial behavioral context an agent would otherwise miss. It stops short of quantifying the allowance or describing pagination/error behavior, which keeps it from 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?

Two tightly packed sentences with the core read operation front-loaded, followed by the cost/usage warning. Every clause earns its place, though the status enumeration inside the first sentence slightly crowds the primary purpose statement.

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

Completeness5/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 compensates by naming the returned fields and the possible status values, and it adds the quota and webhook guidance needed to call this correctly at scale. For a one-parameter read tool, nothing material is missing.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description mentions 'by its id' but adds no format, source, or acquisition guidance (e.g., where the id comes from) beyond what the schema already states.

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?

States a specific verb and resource ('Reads one payment by its id') and immediately scopes it as a single-record read, which implicitly distinguishes it from list_payments. It goes further by enumerating what comes back (status, amounts, expiry, late flag), so an agent knows exactly what this call yields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('read when you need the answer') and when-not-to-use ('never poll in a loop'), plus a concrete alternative pattern ('application code should follow payments with webhooks'). This is the rare case where the guidance actively prevents a common misuse rather than just describing the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.