Skip to main content
Glama
Sign In

Toll — coin, agent and pre-sign checks on Robinhood Chain

by xyz.t0ll
OverviewDiscussionsAdmin

Find a paid API

find_paid_api
Read-onlyIdempotent

Paid APIs (x402) an agent can buy on Robinhood Chain, by what you need (for example "weather", "stock quotes", "BV-7X", or empty for all): each with its resource URL, price, payTo, whether that payTo is the agent wallet its ERC-8004 identity registered (verified, ERC-8478) and how many payments it settled through Toll's x402 facilitator; verified first, one row per operator unless the query names it. From the agent census's x402 endpoints and resources settled through Toll with the x402 bazaar extension. Facts, not a recommendation: verified does not say the seller delivers. Robinhood Chain only.

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": "find_paid_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many rows, 1 to 20 (default 10)
queryNoWhat you want to buy, in a few words (for example "weather" or "stock quotes"); empty lists every operator's best endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world safety, yet the description adds substantial behavior: verified-first ordering, one row per operator unless the query names it, the data sources (agent census, Toll x402 facilitator, x402 bazaar), and an explicit caveat that 'verified' does not mean the seller delivers. That caveat is exactly the kind of epistemic framing an agent needs before acting on results.

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?

It is a single dense sentence with heavy parentheticals, but it is front-loaded with the resource and the selection key, and nearly every clause carries information (fields returned, ordering, dedupe rule, provenance, caveat, scope). Slightly run-on rather than padded.

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?

With no output schema, the description carries the burden of describing returns, and it does: resource URL, price, payTo, the ERC-8004/ERC-8478 verification flag, and settled-payment counts, plus ordering and provenance. For a two-parameter read tool, nothing needed to call or interpret it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and baseline is 3. The description goes beyond it by defining the empty-query semantics and the operator-name matching behavior, which the schema does not state.

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 names a specific resource (paid x402 APIs on Robinhood Chain) and the selection axis (what you need, e.g. "weather", "stock quotes", empty for all). It also fixes scope ('Robinhood Chain only'), so the agent can tell this apart from every sibling tool, none of which deal in paid API discovery.

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 states when the query should be empty ('empty for all'), what to pass when you want a specific capability, and that a query naming an operator returns that operator's rows rather than the deduped view. It gives no explicit when-not-to-use or named alternative, but the intended context is clear.

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

All Toll — coin, agent and pre-sign checks on Robinhood Chain 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