robyn_errorsThe full error taxonomy: every errorCode, whether it is retryable, and the suggested recovery action. Read this once and branch on errorCode instead of parsing messages.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns error codes, retryability, and recovery actions. There is no contradiction with annotations. It provides clear behavioral context for a read-only reference tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences that convey all necessary information without any wasted words. It is front-loaded with the key purpose and includes actionable advice.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no output schema, and no annotations, the description fully covers its purpose and behavior. It tells the agent exactly what data to expect and how to use it (branch on errorCode). This is complete for a reference tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters (schema coverage 100%). The description adds meaning by explaining what the tool returns (error taxonomy), which is valuable beyond the empty schema. Baseline for 0 parameters is 4, but the description is exceptionally clear about the output content.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool provides 'the full error taxonomy: every errorCode, whether it is retryable, and the suggested recovery action.' This is a specific verb-resource pair and distinguishes it from sibling tools which perform actions like check, delegate, submit, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes explicit guidance: 'Read this once and branch on errorCode instead of parsing messages.' This tells the agent exactly when and how to use the tool. However, it does not explicitly state when not to use this tool or provide alternatives, but given it's a reference tool, the guidance is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.