Skip to main content
Glama

The whole evaluation request for my transfer (free, no signature)

recta_request_template
Read-only

Returns the full body of the evaluation request for a corridor, an amount and the route you would use anyway (baseline_provider): you fill only your sender, recipient and gas ceilings, then sign it with recta_prepare_signed_request and recta_send_signed_request.

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>",
      "amount": "<amount>",
      "baseline_provider": "<baseline_provider>"
    },
    "name": "recta_request_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesHow much of source_asset to send, in whole tokens (not cents, not wei): "100" with USDC means 100 USDC. Minimum 3.5 for stablecoins (about 3.5 USD). No maximum.
source_assetYesUppercase asset, e.g. USDC.
latency_classNo
source_networkYesLowercase network as in the service descriptor, e.g. base, ethereum, arbitrum.
guarantee_classNo
baseline_providerYesThe route you would use without Recta (see recta_fit_check's declarable_baselines).
destination_assetYes
destination_networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint and a closed-world scope. The description adds meaningful context beyond them: the returned body is intentionally incomplete (sender, recipient and gas ceilings are left for the caller to fill) and requires a follow-up signing step. It does not cover rate limits or whether the returned quote expires, which would be valuable for a time-sensitive quote-like object.

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 dense sentence that front-loads the return value and then the workflow. The colon-separated clause gets slightly run-on, but no sentence is filler.

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

Completeness3/5

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

For a tool with no output schema, the description should characterize the returned body's structure more than 'the full body of the evaluation request', and two optional parameters are left with zero explanation anywhere. The workflow guidance is solid, but an agent cannot fully predict what it receives or what latency_class/guarantee_class do.

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 only 50% schema coverage, the description should compensate more. It does clarify that baseline_provider is the route you would use without Recta and cross-references recta_fit_check's declarable_baselines, but latency_class and guarantee_class are entirely undocumented in both schema and description despite being part of an 8-parameter tool.

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?

States a specific verb and resource: 'Returns the full body of the evaluation request' for a corridor, amount and baseline route. This distinguishes it from the signing siblings by naming the downstream steps, though the term 'evaluation request' remains somewhat jargon-dependent for an agent unfamiliar with the domain.

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?

Gives an explicit pipeline: call this first, then sign with recta_prepare_signed_request and submit with recta_send_signed_request. It does not contrast with recta_trial_evaluation or state exclusion conditions, so the when-not guidance is absent, but the sequencing guidance is clear.

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.