Skip to main content
Glama
Sign In

Panes

by io.github.logancsack
OverviewDiscussionsAdmin

topup_status

Read-onlyIdempotent

Resumes the stored payment when pending. Paid credit is granted exactly once. Do not submit a new payment after a lost response; poll this URL. pending recommends three seconds between reads.

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": "topup_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

The description does disclose real behavior beyond the annotations: exactly-once credit and a recommended poll interval. However, "resumes the stored payment" and "paid credit is granted exactly once" describe a state-changing side effect, which sits badly against readOnlyHint=true, so the extra detail is partly in tension with the declared safety profile rather than reinforcing it.

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?

Three telegraphic sentences, front-loaded with the pending-state behavior and followed by the no-double-submit warning and cadence, with essentially no filler. The phrasing is terse to the point of ambiguity in the first sentence, but nothing is wasted.

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 single-parameter tool with annotations and no output schema, the description covers the polling story but leaves two gaps an agent needs: what the call returns (states beyond "pending" are only hinted at) and what the id argument refers to. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter "id", and the description never explains what that id identifies (a top-up id, a payment id, or an opaque handle from topup_pay). With one undocumented parameter the description is expected to compensate, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition leads with "Resumes the stored payment when pending" and later "poll this URL," so its status-polling role is only inferable rather than stated: it never says it returns the status of a top-up. An agent can distinguish it from topup_pay only indirectly, via the warning not to submit a new payment after a lost response. The purpose is recognisable but not crisply stated with a verb plus resource.

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?

"Do not submit a new payment after a lost response; poll this URL" is explicit when-to-use guidance tied to a concrete scenario, and the three-second polling cadence for the pending state adds operational context. It stops short of naming when-not to call it or how it relates to topup_quote, so it falls short of a full 5.

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

All Panes toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources