Skip to main content
Glama

Robinhood Chain token risk card ($0.02)

rhc_curve_card
Read-onlyIdempotent

$0.02 USDC per call. Use when you hold or are about to trade one pons v2 token on Robinhood Chain and need a verdict by a fixed public rule, its holders, creator tax, deployer record, ring screen and an exact sell check; to find launches use GET /v1/rhc/launches/recent. Not for Solana mints. Input: address (0x-prefixed pons v2 curve or token address on Robinhood Chain). The verdict (avoid / caution / no_flags_observed, the fixed public rule LABELS rhc_verdict at /v1/labels, with basis, reason and up to three reasons carrying their evidence and measured base rate): avoid while a charged buy pays >= 618 bps of snipe tax or when the 3 s holder structure matched the ring rule; caution on a creator tax >= 500 bps, a top holder >= 50%, a deployer with >= 3 earlier launches and no graduation, a curve at <= 50% of its peak price 30 min after launch without graduating, a missing or pending 3 s snapshot, or a completed or graduated curve. deployer_record: the deployer's earlier launches on our tape, how many graduated or matched the ring rule at 3 s, the median peak and terminal multiples. sell_check: buy and sell tax in bps, the exact quote for selling 1% of supply and a 0.01 ETH round trip in bps from the recorded reserves (graduated tokens: the pool's taxes, no quote). Full structure card for ONE pons v2 curve on Robinhood Chain, addressed by curve or token address (0x…): launch facts (block, deployer, pair token, graduation threshold), raised / progress / price multiple vs launch (exact curve reserves, ETH-paired curves), the launch's trade fee and creator tax in bps (fees block; the creator tax is charged on every buy and sell and is invisible to three-word event parsers), snipe-tax activity, holder ledger concentration (top-1 / top-5 / HHI / deployer share), same-block direct-buy cluster share and wallets, max direct buys in one 100 ms block, terminal-vs-direct route mix with terminal holdings share, flow (buys / sells / unique buyers / new buyers in the last 2 and 6 s / last trade age / volumes), lifecycle (completed / graduated blocks and delays, refunds), the trade_cost block (for a 0.01 and a 0.05 ETH clip at the curve's reserves now, exact with fee and creator tax on both legs and own impact: fill price vs marginal, the immediate round trip, and the price rise from now needed to break even), and the ring block: the coordinated-cluster screen (unique_buyers >= 8 and same-block direct-buy cluster share >= 0.5) our own capture measured at 14.5% of launches, 47% dumped, median 0.37x terminal; matching timing is not proof of coordination. coverage=full for curves launched inside our event window (last ~2 h, trades observed from block 0); thin = launch facts + lifecycle only, with a reason. Always 200 for a valid address. Returns JSON envelope with data{curve, token, status, coverage, raised, snipe_tax, structure, flow, lifecycle, verdict, basis, reason, reasons, deployer_record, sell_check}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes0x-prefixed 40-hex pons v2 curve OR token address on Robinhood Chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"0x-prefixed 40-hex Pons V2 curve OR token address on Robinhood Chain"New value: +"0x-prefixed 40-hex pons v2 curve OR token address on Robinhood Chain"
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description goes beyond by disclosing a per-call cost, the exact verdict rules and thresholds, the ring-screen detection parameters, base rates, and that it always returns 200 for valid addresses. It also clarifies the distinction between full and thin coverage, adding substantial behavioral context.

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 description is long and dense, but every sentence carries specific operational detail (cost, coverage, verdict rules, output fields). It is well-structured with clear sections (verdict, deployer_record, sell_check, trade_cost, ring block) and front-loads the cost and usage. While not concise, the verbosity is justified given the tool's complexity and lack of output schema.

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 fully enumerates the response envelope fields (data{curve, token, status, coverage, raised, snipe_tax, structure, flow, lifecycle, verdict, basis, reason, reasons, deployer_record, sell_check}) and explains each major block (verdict, deployer_record, sell_check, trade_cost, ring). It also covers edge cases like coverage=thin and always-200 behavior. Nothing essential for an agent to call it correctly 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% and the parameter description is already clear ('0x-prefixed 40-hex pons v2 curve OR token address'). The description adds a minor clarification about accepted address types and reiterates the format, but does not significantly extend meaning beyond the schema. Baseline 3 is raised to 4 because the description reinforces the dual nature of the address (curve or token) and ties it to the tool's scope.

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 clearly states the tool produces a risk card with a verdict for a single pons v2 curve on Robinhood Chain, specifying exact inputs and outputs. It differentiates from siblings by explicitly stating it is not for Solana mints and referencing the sibling endpoint for launches.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance ('Use when you hold or are about to trade one pons v2 token on Robinhood Chain and need a verdict...') and when-not ('Not for Solana mints'). It also directs to a sibling tool for launch discovery and explains coverage conditions (full vs thin) based on launch timing.

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