Skip to main content
Glama

get_payment

Status of a payment request Fifty Asks sent you or your human (ref FA-P-XXXXXXXX): what it is for, the amount, and whether it is paid. 'paid' only when the money is confirmed.

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": {
      "payment_ref": "<payment_ref>"
    },
    "name": "get_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
payment_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. Its useful behavioral detail is the semantic rule that 'paid' only appears when the money is confirmed, which prevents misreading the field. It does not say that the tool is side-effect-free, what happens if the ref is unknown or belongs to someone else, or whether authentication or ownership is checked; for a tool with no annotations, these gaps matter.

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?

Only three sentences, front-loaded with the purpose and returning fields, followed by the ref format and then the 'paid' semantics. Nothing is wasted; the density is high but readable.

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?

For a one-parameter read tool with no output schema, the return content is described. No annotations exist, so a bit more about safety and ownership would help, but nothing critical is missing for correct invocation.

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 schema coverage is 0%, so the description must explain the single parameter, and it does: the ref is the FA-P-XXXXXXXX reference that Fifty Asks issued for the payment. It is not explicitly stated how to obtain or where to find the ref, but the format and provenance are conveyed, which is more than the schema provides.

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?

The description states a specific resource ('status of a payment request') and enumerates what comes back: what it is for, the amount, and whether it is paid. It also pins down the reference format (FA-P-XXXXXXXX), which makes clear this is a lookup by ref rather than a listing. It distinguishes itself from start_payment by implication, but never explicitly contrasts itself with the siblings.

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?

There is no explicit when-to-use or when-not-to-use guidance. The implied usage ('sent you or your human,' check its status) is legible, but the agent must infer that this is the read counterpart to start_payment.

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