Skip to main content
Glama

Check a top-up

top_up_status
Read-only

Check a top-up from top_up by its topup_id. status: open (waiting for payment), paid (credited; check the balance with whoami), expired (link ran out or payment failed: call top_up again) or under_review (a payment arrived and is checked by hand). next says what to do; never ask your human to pay twice. Poll every 5 seconds while they pay, else later. Only the agent that made it, or one of the same owner, can read it; others get topup_not_found.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topup_id": "top_exampleexampleexample2"
    },
    "name": "top_up_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
topup_idYesThe topup_id that top_up returned (top_...).
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topup_id / description
      Previous value: -"topup_id from top_up."New value: +"The topup_id that top_up returned (top_...)."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "topup_id": "top_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / topup_id / description
      Added value: +"topup_id from top_up."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description goes well beyond them: an access-control rule (only the creating agent or same owner may read; others get topup_not_found), the full status vocabulary with meanings, and a pointer to the 'next' field. These are non-obvious operational facts an agent could not infer from the annotations.

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?

Front-loaded with the action, then the state table, then operational rules — good ordering with no filler. It is densely packed with colons and semicolons, and compressed fragments like 'else later' read as terse rather than precise, costing a point.

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?

No output schema exists, so the description carries the return semantics itself and does so: it enumerates the status values and names the 'next' field that tells the agent what to do. For a two-parameter read tool, nothing needed to call or interpret it 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?

Schema coverage is 100%, so the schema already documents both parameters including the top_... format. The description reinforces that topup_id comes from a prior top_up call but adds no syntax or format detail, and the optional passport_token is not discussed at all — baseline 3.

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 ('Check a top-up') and pins the identifier to its origin ('from top_up by its topup_id'), which cleanly separates it from top_up (creation) and whoami (balance). An agent can pick it out of the sibling list without opening the schema.

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?

Gives explicit per-state routing: paid -> check balance with whoami, expired -> call top_up again, under_review -> hand-checked. It also supplies polling cadence ('every 5 seconds while they pay, else later') and a hard behavioral rule ('never ask your human to pay twice'), which is exactly the when/when-not guidance this dimension rewards.

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.