Skip to main content
Glama

Payment status

get_payment_status
Read-onlyIdempotent

The status of a payment order made by subscribe: pending, paid, failed, expired, cancelled. When paid, get_account shows the plan and credits. [REST: GET /api/billing/orders/{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": {
      "order_id": "<order_id>"
    },
    "name": "get_payment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe order id from subscribe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral value by disclosing the full set of returned states (pending, paid, failed, expired, cancelled) and the REST endpoint, which tells the agent what outcome space to handle.

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 compact sentences plus an endpoint tag; the status enumeration and the follow-up tool pointer are front-loaded with no filler. Nothing could be cut 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 appropriately carries the return-value burden by listing every possible status, and the single required parameter is fully covered by the schema. It is essentially complete for a simple one-parameter status lookup.

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 coverage is 100% and the order_id property is already described as 'The order id from subscribe'. The description restates that same provenance and adds no format, sourcing, or lookup guidance beyond the schema, so the baseline 3 applies.

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 names the resource (a payment order's status) and its origin ('made by subscribe'), and enumerates the five possible states, so an agent can distinguish it from siblings like get_account or get_subscription. The verb 'get' is only implied by the tool name, which keeps it short of a perfect 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?

Usage is implied rather than stated: call this to check an order created by subscribe, then move to get_account once payment is paid. That next-step pointer is genuinely useful, but there is no explicit 'use this when / not when' framing or named alternative for other cases.

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