SafeRoute

verify_swap_execution

Verify a standard-mode SafeRoute Base execution against its signed receipt. Free; referral payouts remain disabled.

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": {
      "transactionHash": "<transactionHash>",
      "receipt": "<receipt>",
      "receiptSignature": "<receiptSignature>"
    },
    "name": "verify_swap_execution"
  }
}

Input Schema

Name	Required	Description	Default
`receipt`	Yes
`transactionHash`	Yes
`receiptSignature`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It discloses only that the tool is free and disables referral payouts, but does not describe side effects, return behavior, or whether it is a read-only operation. This is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is only two sentences, front-loaded with the main purpose. The second sentence adds a concise behavioral note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity is moderate with 3 required params and a nested object, but no output schema and no annotations. Description does not explain how to construct the receipt, what transactionHash refers to, or expected response. Minimal guidance for correct invocation.

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 coverage is 0%, and the description only mentions 'signed receipt', providing minimal meaning for receipt and receiptSignature. transactionHash is not explained, and receipt structure is unclear. Description does not compensate for missing schema descriptions.

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?

Description uses specific verb 'Verify' and identifies exact resource: 'standard-mode SafeRoute Base execution' against 'signed receipt'. This clearly distinguishes from sibling tools like check_base_swap and get_safe_swap_quote.

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?

Description gives context that this verifies execution against a signed receipt, but does not explicitly mention when to use it instead of alternatives like check_base_swap or get_safe_swap_quote. The note 'Free; referral payouts remain disabled' hints at limitations but lacks explicit guidance.

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

All SafeRoute tools Inspect

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

Need Help?