1gateway

Robinhood Chain stock tokens: registry verification, share multiplier, Chainlink feed health, 24/5 market state

rh_stock_tokens

Use when an agent integrates tokenized equities on Robinhood Chain (4663). Input: optional symbols (<=20), address, limit (1-100), feedOnly. Output: JSON per token: on-chain uid/symbol checked against the public registry, uiMultiplier vs registry, pending multiplier, paused, supply, Chainlink feed age/stale/lag, reference total-return value; US 24/5 session state. Reference signals, not market data or advice. Example: ?symbols=AAPL,TSLA Price: $0.003 USDC (Base or Solana) via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rh_stock_tokens"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Tokens returned (1-100, default 25)
`address`	No	One token contract; not in the registry → 404 (not charged)
`symbols`	No	Comma list of up to 20 tickers (AAPL,TSLA). Default: all, alphabetical
`feedOnly`	No	true = only tokens with a Chainlink feed

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.9/5.0

Behavior4/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 well: it enumerates the verified output fields (registry uid/symbol, uiMultiplier vs registry, pending multiplier, paused, supply, Chainlink feed age/stale/lag), states the 24/5 session state, discloses the x402 price of $0.003 USDC, and disclaims 'reference signals, not market data or advice'. It does not mention rate limits or error behavior beyond the schema's 404 note.

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?

The trigger is front-loaded, and inputs and outputs are enumerated compactly. The price sentence is appended after the example in a slightly awkward spot, but every sentence still carries information.

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

Completeness4/5

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

There is no output schema, so the description must explain return values, and it does thoroughly, field by field, plus session state and a disclaimer. Only error handling and rate/auth behavior beyond the x402 price are left out.

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?

Schema description coverage is 100%, so the schema already documents all four parameters. The description restates the inputs and adds a concrete example (?symbols=AAPL,TSLA), but adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb-and-resource pair (verify/integrate tokenized equities on Robinhood Chain 4663) and scopes it to registry checks, multipliers, and feed health. It is clearly distinguishable from generic sibling tools like base_token_info or token_report. What's missing is an explicit contrast with those siblings.

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?

It gives a clear trigger: 'Use when an agent integrates tokenized equities on Robinhood Chain (4663)'. There is no when-not guidance and no named alternatives among the many token-info siblings, so it stops short of full routing guidance.

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

All 1gateway tools Inspect

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

Need Help?