Skip to main content
Glama

Robyn — Gasless Cross-Chain for AI Agents

by io.github.ox31461

Settle value privately, gasless, best-route — one call

robyn_settle

The one-verb primitive. Say where value should go; Robyn returns the best route (all rails compared), the gasless method (no native token needed), the privacy posture that will apply (API-relay + private mempool where available + uniform shape), and what the settlement receipt will prove — in a SINGLE call. It collapses quote + preflight + prepare. Planning only: it never broadcasts — sign + submit via robyn_submit. Add private:true to request private-mempool execution where an endpoint exists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesvalue in source-token base units (e.g. "25000000" = 25 USDC)
privateNorequest private-mempool execution (default: auto where an endpoint exists)
toChainYesdestination chain id or non-EVM name
toTokenNo
fromChainYessource chain id or "stellar"/"solana"/"tron"/"bitcoin"
fromTokenNosymbol or address; omit for the chain default (USDC)
toAddressYesrecipient on the destination
fromAddressNosender — sets fee tier and free-netting eligibility

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full burden and delivers: it never broadcasts, returns route/method/privacy/receipt, and offers private-mempool request. It discloses the privacy posture (API-relay + private mempool + uniform shape) without contradicting any structured data.

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?

Four sentences, front-loaded with 'The one-verb primitive.' Some slight redundancy between 'in a SINGLE call' and 'It collapses quote + preflight + prepare', but no fluff. Structured with em-dashes and semicolons for readability.

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?

For a complex planning tool with 8 parameters and no output schema, the description covers core functionality, planning-only behavior, and the submit path. It doesn't specify exact return values, but states what the receipt will prove, which is sufficient for initial understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high at 88%, so baseline is 3. The description adds value by explaining the private:true parameter meaning and how to use it, plus the conceptual 'one call' context. It doesn't deeply elaborate on all 8 parameters, but that's not necessary given schema richness.

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 this is the 'one-verb primitive' that returns the best route, gasless method, privacy posture, and settlement receipt proof in a single call. It explicitly distinguishes itself from siblings by collapsing quote + preflight + prepare, making it a compound planning tool.

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

Usage Guidelines5/5

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

Provides explicit guidance: 'Planning only: it never broadcasts — sign + submit via robyn_submit.' This tells when to use (planning) and when not to (broadcasting), naming the alternative. It also advises on the private:true parameter for requesting private-mempool execution.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as robyn_quote, robyn_prepare, robyn_settle, robyn_cross_chain, robyn_plan, robyn_preflight, and robyn_preflight_full, all involving routing or quoting. Although descriptions are detailed, the high number of subtly different tools makes selection error-prone.

Naming Consistency5/5

All tools follow a consistent <prefix>_<verb/noun> pattern, with robyn_ and null_ as clear category prefixes. Verbs like prepare, submit, verify and nouns like quote, plan, mesh are highly predictable throughout.

Tool Count2/5

With 70 tools, the count far exceeds the 25+ heavy threshold. While the service scope is broad (payments, messaging, netting, Plus, yield, etc.), many tools could be merged or tiered, making the set feel overly large and burdensome for an agent.

Completeness4/5

The surface covers the full lifecycle from quoting, planning, submitting, verifying, auditing to messaging, custody, yield, and mandates, plus sandbox, lint, and recipes. A few advanced operations like cancellation or revocation are missing, but no critical gaps remain.

Resources