Skip to main content
Glama

Payment status

payment_status
Read-onlyIdempotent

Check a Rozo order: whether the deposit arrived, bridging/payout progress, and whether the OpenRouter or other AI service invoice settled. Pass rozoPaymentId for orders that have one, or url (the payment link) for TRON / TON orders, which have none. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPayment link of a TRON / TON order (use instead of rozoPaymentId).
rozoPaymentIdNoOrder UUID returned by create_deposit_order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Payment link of a TRON / TON order (use instead of rozoPaymentId).",
      +  "maxLength": 512,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "rozoPaymentId"
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower, yet the description still adds real content by specifying which lifecycle stages the response reflects (deposit, bridging/payout, invoice settlement). It does not describe polling expectations, caching, or freshness of the status, which would have made it 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 compact sentences lead with the purpose and outcome facets, then follow with the identifier-selection rule. The closing 'Read-only.' is redundant with readOnlyHint=true and is the only wasted text.

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 does the necessary work of summarizing what the status reflects, and it fully covers how to identify an order. Minor gaps remain around response shape and whether repeat polling is expected, but nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds rationale the schema lacks: that TRON / TON orders have no payment ID and therefore must be addressed by payment link. That explains the mutual exclusivity rather than merely restating the parameter descriptions.

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 a specific verb and resource ('Check a Rozo order') and enumerates the three states it reports: deposit arrival, bridging/payout progress, and AI-service invoice settlement. It scopes itself to 'Rozo order', which implicitly separates it from the Stellar-wallet order siblings, though it never names the sibling it might be confused with.

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?

It gives clear selection logic between the two input modes ('rozoPaymentId for orders that have one, or url … for TRON / TON orders, which have none'), which is genuinely useful. However, it offers no when-to-use versus when-not-to-use framing against alternatives such as stellar_wallet_order_status, so the guidance is implied rather than explicit.

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.