Skip to main content
Glama
Sign In

Robyn — Gasless Cross-Chain for AI Agents

by io.github.ox31461
OverviewDiscussionsAdmin

Prove a payment request was satisfied on-chain

robyn_payment_request_settlement

After paying, prove it: re-checks the transfer against the DESTINATION CHAIN and confirms the payee was paid at least the amount requested. Returns paid=true only on a verified on-chain result; paid=null means undetermined, which is NOT evidence you satisfied the 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": {
      "request": "<request>",
      "signature": "<signature>",
      "transferId": "<transferId>"
    },
    "name": "robyn_payment_request_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
signatureYes
transferIdYesthe transfer that paid it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden. It discloses the verification logic, the meaning of paid=true (verified on-chain result) and paid=null (undetermined, not evidence), which is crucial for correct interpretation.

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 two sentences, front-loaded with 'After paying, prove it', and every sentence adds necessary behavioral insight. No redundant or filler content.

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?

The description adequately covers the core purpose and primary return semantics (paid=true/null), but with no output schema it does not fully explain the complete response shape or the role of request/signature parameters. It is usable but has gaps for a 3-parameter tool with nested objects.

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 description coverage is only 33% (only transferId has a description). The description adds no explicit meaning for the 'request' object or 'signature' string, and only indirectly relates to the transfer via the transferId. It does not compensate for the schema gaps.

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 a specific verb and resource: 'prove it' by re-checking the transfer against the DESTINATION CHAIN and confirming the payee was paid. It differentiates from siblings by emphasizing on-chain verification and the payee amount requirement.

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 clear context: 'After paying, prove it' indicates when the tool should be used. However, it does not explicitly mention alternatives or when not to use it, which would fully distinguish it from sibling tools like robyn_payment_request_verify.

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