Skip to main content
Glama

Swap status

swap_status
Read-only

Outcome of a swap by its XRP Ledger transaction hash: XRP payment validated, THORChain observed it, swapping, coins sent (with outbound hashes), or refunded.

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": {
      "tx": "<tx>"
    },
    "name": "swap_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesThe 64-character XRP Ledger transaction hash of the signed Payment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating the outcome states including refunds and outbound hashes, but it does not say which states are terminal, whether unknown hashes error or return empty, or how polling should work.

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?

One dense, front-loaded sentence with no filler; the outcome list is compact. It is slightly list-heavy but every clause carries meaning.

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-only lookup with no output schema, the description's outcome enumeration does most of the work an agent needs to interpret a response. The remaining gap is lifecycle semantics (terminal states, polling), which is minor for this complexity.

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?

With a single parameter at 100% schema description coverage, the schema already explains the 64-character hash. The description only reinforces that it is the hash of the *signed Payment*, a small addition over what the schema states.

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 resource (swap outcome) and the lookup key (XRP Ledger transaction hash), and enumerates the possible states it reports. It is clearly distinct from quote_swap and build_swap_tx by being a status lookup, though it never states that contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says this is the post-submission polling step, how often to call it, or that build_swap_tx/quote_swap cover the earlier stages. The usage context is only weakly implied by the mention of a signed Payment's hash.

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