Skip to main content
Glama
ExpertVagabond

robinhood-chain-mcp

x402_build_payment_requirements

Build the payment requirements object for HTTP 402 (Payment Required) responses by specifying payee address and amount, enabling paid resource access.

Instructions

Build the paymentRequirements object a resource server returns in its HTTP 402 response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoUSDG
payToYesAddress that receives payment
amountYesHuman amount, e.g. '0.01'
resourceNoURL of the paid resource
descriptionNo
maxTimeoutSecondsNo
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only says 'builds', implying a pure construction, but no detail on side effects, auth requirements, or error handling.

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?

Single sentence with no redundancy, but under-specified for its parameter count and complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no output schema, and no annotations, the description fails to explain the output or how the object is used, leaving the agent with insufficient context.

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 50%, and the tool description adds no additional meaning to parameters. It does not compensate for missing parameter descriptions.

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 specifically states it builds the paymentRequirements object for an HTTP 402 response, clearly distinguishing from sibling tools like x402_build_payment_payload.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives or when not to use it. The description lacks context for decision-making.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ExpertVagabond/robinhood-chain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server