Skip to main content
Glama
Sign In

Robyn — Gasless Cross-Chain for AI Agents

by io.github.ox31461
OverviewDiscussionsAdmin

Move value cross-chain, gasless

robyn_cross_chain

Plan a gasless cross-chain move and get the exact payload to sign. This hosted server never holds your key: call this, sign what it returns with your own wallet, then call robyn_submit to have the relayer broadcast it and pay the gas.

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>",
      "amount": "<amount>",
      "toChain": "<toChain>",
      "toToken": "<toToken>"
    },
    "name": "robyn_cross_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesamount in fromToken base units
toChainYes
toTokenYestoken address / symbol on the destination
fromChainYes
fromTokenYestoken address on the source chain
toAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description bears full responsibility. It explains the behavior: returns a payload to sign, the server does not hold the key, and the relayer broadcasts on submission. It lacks details on error handling or rate limits but is transparent about the core workflow and security.

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?

Two sentences deliver essential information efficiently. The most critical action ('Plan a gasless cross-chain move') is front-loaded, and every sentence adds value without redundancy.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description covers the overall purpose and workflow adequately. It lacks detail on the returned payload structure and error scenarios, but the presence of sibling tools like 'robyn_route_status' may cover status tracking.

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 50% with only three parameters described in the schema. The description adds no additional meaning or context for any parameters, missing an opportunity to clarify formats (e.g., chain IDs as numbers or strings) or the optional 'toAddress' field.

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 plans a gasless cross-chain move and returns a payload to sign. It distinguishes itself from siblings by referencing 'robyn_submit' for submission, making the purpose specific and unambiguous.

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?

The description provides a sequential workflow: call this, sign the returned payload, then call 'robyn_submit'. It also notes the server never holds the key, which is a key usage caveat. However, it does not explicitly exclude other sibling tools or state when not to use this tool.

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 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