Skip to main content
Glama
Sign In

Soheil Router

by fi.soheil
OverviewDiscussionsAdmin

Trade status

get_trade_status
Read-only

Where a sent trade stands, from its transaction on chain: PENDING, DONE (with what was paid and received; for a bridge, once paid on the destination), REFUNDED (a bridge transfer paid back on the source network), FAILED, NOT_FOUND or NOT_OURS. Needs an API key.

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": {
      "chainId": "<chainId>",
      "txHash": "<txHash>"
    },
    "name": "get_trade_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashYesThe transaction hash, 0x + 64 hex
chainIdYesThe network the trade was sent on

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?

With readOnlyHint=true and openWorldHint=true already covering safety and external-world access, the description adds meaningful behavioral context: the status values and their meanings, including bridge-specific DONE and REFUNDED semantics. It also notes the API-key requirement, though it does not explain eventual consistency or polling behavior.

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?

The description is a single front-loaded sentence that efficiently conveys the purpose and status meanings. The parenthetical bridge explanations are dense but relevant, and there is no superfluous prose.

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 two-parameter read-only status lookup without an output schema, the description covers the key return values and clarifies bridge-specific cases. It leaves some operational details unstated, such as whether NOT_FOUND means not indexed yet, but it is otherwise sufficient.

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 both parameters are already documented. The description adds only that the transaction identifies a sent trade and that the chain is the one the trade was sent on, which largely restates the schema rather than adding new syntax or format details.

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 clearly states that this tool reports where a sent trade stands based on its on-chain transaction, and it enumerates the possible outcomes. It distinguishes itself implicitly from quote/network/API-info siblings by focusing on an already-sent trade, but it does not explicitly name those alternatives.

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?

The phrase 'sent trade' and the need for a transaction hash and chain imply usage after a trade has been submitted. There is no explicit when-to-use vs get_quote guidance, nor any exclusion or polling guidance for NOT_FOUND/PENDING cases.

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

All Soheil Router 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