Skip to main content
Glama

Is my transfer covered? (free, no signature)

recta_fit_check
Read-only

Call first, before a cross-chain stablecoin transfer: whether Recta covers the corridor, which routes it compares, which route you can declare as yours, and the contracts a route would touch. Unsigned, free, never reveals a route or a saving.

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": {
      "source_network": "<source_network>",
      "source_asset": "<source_asset>",
      "destination_network": "<destination_network>",
      "destination_asset": "<destination_asset>"
    },
    "name": "recta_fit_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_assetYesUppercase asset, e.g. USDC.
source_networkYesLowercase network as in the service descriptor, e.g. base, ethereum, arbitrum.
destination_assetYes
destination_networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds genuinely useful context beyond that — 'Unsigned, free, never reveals a route or a saving' — telling the agent no signature is needed and that the response withholds pricing/routing detail. It does not describe response shape, determinism, or rate limits.

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?

A single front-loaded sentence that leads with the call-first guidance before enumerating outputs; no filler. The four-clause list is dense but each clause earns its place.

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?

No output schema exists, and the description compensates by enumerating the four things returned (coverage, compared routes, declarable route, touched contracts). The main gap is the undocumented destination-side parameters, which leaves the agent guessing at input format.

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 only 50%: source_asset and source_network carry casing conventions, but destination_asset and destination_network are undocumented in both schema and description. The description's talk of a 'corridor' implies the pair matters but never states that the destination parameters take the same lowercase-network/uppercase-asset conventions.

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 check the tool answers — whether Recta covers the corridor — plus the four outputs it returns (routes compared, declarable route, contracts touched). The closing line 'never reveals a route or a saving' implicitly distinguishes it from savings/quote-oriented siblings like recta_saving_odds.

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

Usage Guidelines4/5

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

Explicit sequencing guidance: 'Call first, before a cross-chain stablecoin transfer' tells the agent exactly where this fits in a workflow. It stops short of naming an alternative tool or stating when not to use it, which keeps it from a 5.

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.