Robyn — Gasless Cross-Chain for AI Agents

Quote a gasless cross-chain route

robyn_quote

Best gasless route to move a token from one Robyn chain to another. Returns estimated output, the bridge used, duration, and the Robyn fee. Read-only — moves nothing. IMPORTANT: check quoteOnly on the response. If it is true the corridor can be PRICED but NOT settled — execute will refuse it with UNSUPPORTED_DIRECTION — so present that quote as a price comparison only and do not tell the user it can be sent. quoteOnlyReason says why. Absent/false means executable.

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": {
      "fromChain": "<fromChain>",
      "fromToken": "<fromToken>",
      "toChain": "<toChain>",
      "toToken": "<toToken>",
      "amount": "<amount>"
    },
    "name": "robyn_quote"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	amount in fromToken base units (e.g. "25000000" = 25 USDC)
`toChain`	Yes	destination chain id, or "stellar"
`toToken`	Yes	token address / symbol on the destination
`fromChain`	Yes	source chain id, or "stellar"
`fromToken`	Yes	token address on the source chain (0x0000…0000 for native)
`toAddress`	No	recipient on the destination chain
`fromAddress`	No	sender — determines membership (fee tier) AND whether a free netting path is available between these two accounts

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 2, 2026

addedInput schema / properties / fromAddress

Added value: +{
+  "description": "sender — determines membership (fee tier) AND whether a free netting path is available between these two accounts",
+  "type": "string"
+}

First observedJul 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature ('moves nothing') and reveals a critical behavioral nuance: the quoteOnly field indicates whether the route is executable, with detailed instructions on how to interpret and present it. This is exemplary transparency beyond typical tool descriptions.

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?

The description is five sentences, front-loaded with the primary purpose, then the essential behavioral caveat. It uses bold and uppercase for the critical part, making it scannable. No unnecessary words or repetition.

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

Completeness5/5

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

For a quote tool with no output schema, the description covers everything needed: return fields, read-only behavior, the quoteOnly exception, its reason, and the default executable status. This fully equips the agent to correctly interpret and present the tool's response in all cases.

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?

The input schema already provides complete descriptions for all 7 parameters (100% coverage), so the baseline is 3. The description adds no additional parameter-level meaning beyond the schema, which is acceptable given the schema's thoroughness.

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?

The description clearly states the tool's function: 'Best gasless route to move a token from one Robyn chain to another' and lists the returned fields (estimated output, bridge, duration, Robyn fee). It explicitly says 'Read-only — moves nothing,' distinguishing it from execution tools like robyn_cross_chain or robyn_submit.

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?

Provides strong contextual guidance: it says to use the tool for quoting and explicitly warns about quoteOnly=true cases, instructing the agent to present such quotes as price comparison only and not as sendable. It references that 'execute will refuse it' but does not name the specific alternative tools (e.g., robyn_cross_chain) explicitly, so it falls just short of a 5.

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

All Robyn — Gasless Cross-Chain for AI Agents 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.