Skip to main content
Glama
Sign In

Robyn — Gasless Cross-Chain for AI Agents

by io.github.ox31461
OverviewDiscussionsAdmin

Messaging v2 — anchoring proof for a feed row

robyn_message_anchor_proof

Merkle inclusion proof for an anchored row id: leaf, path, root, the signer’s EIP-191 signature over the batch statement and the on-chain tx when enabled. Verify locally with plus-sdk verifyAnchorProof(). Read-only.

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": {
      "id": "<id>"
    },
    "name": "robyn_message_anchor_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes16-hex feed row id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so impressively. It explicitly states 'Read-only', lists the expected proof fields, and discloses the conditional 'when enabled' for the on-chain transaction. It could mention error behavior but covers the essential operational traits well.

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 concise yet information-dense, pack intent, content, verifiability, and safety into a few lines. No filler or redundancy.

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 single-parameter tool with no output schema, the description covers the proof contents, the verification method, the conditional transaction field, and the read-only nature. This fully compensates for missing structured metadata.

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 schema already fully describes the single parameter as a '16-hex feed row id' (100% coverage), and the description's 'anchored row id' adds no new semantics. A baseline of 3 is correct since the schema handles the parameter documentation without needing additional description.

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?

The description clearly identifies the tool as providing a Merkle inclusion proof for an anchored row id and specifies the proof components. It doesn't explicitly contrast with sibling proof/verification tools, so it's clear but lacks direct sibling differentiation.

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

Usage Guidelines3/5

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

It gives practical guidance to 'Verify locally with plus-sdk verifyAnchorProof()', which implies how to use the output, but it doesn't position this tool against alternatives or state when not to use it. Usage context is conveyed only through the proof purpose, so it's barely adequate.

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