Skip to main content
Glama

Robinhood launch feed

robinhood_launch_feed
Read-onlyIdempotent

New token launches on Robinhood Chain (chain 4663) with a real Uniswap v4 simulated buy-and-sell test graded CAN_EXIT, EXPENSIVE, THIN_POOL, TRAP or CANNOT_SELL. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
gradeNofilter by grade: CAN_EXIT, EXPENSIVE, THIN_POOL, TRAP, CANNOT_SELL or UNTESTED
limitNorows per page, 1 to 100 (default 20)
sinceNocursor: return only rows with seq above this number (0 or omitted = newest)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a $0.01 per-call cost, the accepted x402 payment assets (USDC on Arc/Base/Solana, XNT on X1), and the simulated-grading methodology. The only gap is the mild tension between readOnlyHint=true and a tool that spends money and 'completes the purchase' in-call, which an agent would want called out explicitly.

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?

Three sentences, front-loaded with what the feed contains, then the grade taxonomy, then cost and the payment loop. No filler and no repetition of the title.

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?

No output schema exists, so the description must carry return semantics; it conveys the row concept (launches with grades) but not the actual fields an agent would receive. For a paid, open-world feed this is close to complete, with the response shape the main remaining unknown.

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 the baseline is 3, but the description goes beyond the schema by explaining the two-phase lifecycle of the `payment` parameter (fetch terms unsigned, then resubmit signed) rather than just its format. `grade`, `limit` and `since` are left to the schema.

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?

States a specific verb and resource ('New token launches on Robinhood Chain (chain 4663)') plus the distinguishing feature, a simulated buy-and-sell test producing five named grades. The explicit chain ID lets an agent separate it from base_launch_feed without opening either schema.

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?

Gives a precise operating procedure: call once without `payment` to obtain terms, sign with your own wallet, call again with `payment`. It never explicitly names an alternative tool or states when not to use this one, so sibling routing (e.g. base_launch_feed for another chain) must be inferred from the chain scoping.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources