Skip to main content
Glama
Sign In

Robyn — Gasless Cross-Chain for AI Agents

by io.github.ox31461
OverviewDiscussionsAdmin

Get the consent text a user must sign to open a netting account

robyn_netting_enroll_payload

Returns the EXACT message the account must sign with its OWN key to open a custodial balance. This endpoint holds no key and enrols nobody — it returns the text; the user signs it, then POST {address, signature} to /api/netting/enroll. CUSTODIAL — this is the ONE part of Robyn that holds your balance; every other tool here moves funds without Robyn ever holding them. Tell the user that plainly before they enrol. Show the user the full consent text before they sign it: it states that the balance is held by Robyn, is not insured, and could be lost.

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": {
      "address": "<address>"
    },
    "name": "robyn_netting_enroll_payload"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesthe address that will own the netting account

Schema Changelog

Changes observed during successful MCP inspections.

  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 responsibility for behavioral disclosure. It reveals that the tool does not actually enroll anyone, does not hold keys, and that the resulting balance is custodial, uninsured, and 'could be lost.' This goes far beyond the name/schema and is essential context for the agent.

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 compact yet information-dense, starting with the primary purpose and then adding essential workflow and risk warnings without redundancy. Every sentence earns its place, and the structure front-loads the most important information.

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 one-parameter tool with no output schema, the description is self-sufficient: it explains what the tool returns, how to use it, and the critical custodial risks. It also provides the follow-up endpoint, making the entire flow clear.

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 description already fully documents the single parameter 'address' as 'the address that will own the netting account.' The description adds no additional parameter-specific semantics beyond what the schema provides, so baseline 3 applies.

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 'Returns the EXACT message the account must sign with its OWN key to open a custodial balance.' It distinguishes itself from sibling tools by explicitly noting it 'holds no key and enrols nobody,' making it unambiguous that this is a payload-generation tool rather than an enrollment action.

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?

The description provides a complete usage workflow: get the text, user signs it, then POST {address, signature} to /api/netting/enroll. It also gives critical guidance on when to use this tool (before enrolling) and contrasts it with other tools by highlighting that 'every other tool here moves funds without Robyn ever holding them.'

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