Skip to main content
Glama
Sign In

robinx-mcp

by io.github.jamhimself
OverviewDiscussionsAdmin

Pre-trade check (one call)

robinx_check
Read-only

The pre-trade check in one call for a Robinhood Chain token: clear (no rule-based blocker) or the blockers and warnings, each named, with the readings behind them — the verdict with its reasons, the deployer's record, holder concentration, the market, the measured X callers who named the token (coordinated clusters count once), the contract template. Free under a daily per-IP cap of 100, $0.02 over x402 past it, every plan key covers it. Rule-based observations, never a recommendation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "robinx_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken contract address 0x…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost and throttling mechanics (free under a 100/day per-IP cap, $0.02 over x402, plan keys cover it), a key interpretive caveat ('rule-based observations, never a recommendation'), and non-obvious semantics (coordinated clusters count once in the caller count). These are exactly the traits annotations cannot express.

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?

Front-loaded with the verdict outcome before the em-dash enumeration of what is included; pricing and disclaimer close it cleanly. The middle enumeration is dense but every item conveys a distinct returned signal, so there is little filler.

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?

With no output schema, the description carries the burden of describing return content, and it does so thoroughly: outcome framing, per-block readings, plus cost and disclaimer. It stops short of explaining error cases (invalid address, unknown/unindexed token) or the shape of a 'blocker' versus a 'warning'.

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?

Only one parameter ('token') and the schema already documents it at 100% coverage as a 0x… contract address. The description adds only the constraint that the token be a Robinhood Chain token, which is mild added meaning over the schema — the baseline 3 for full schema coverage 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?

States a specific resource and scope: a full pre-trade check for a Robinhood Chain token, delivered in one call, returning either 'clear' or named blockers/warnings. The composition list (verdict, deployer record, holder concentration, market, X callers, contract template) makes it distinguishable from the narrower siblings like robinx_verdict or robinx_deployer, though it never names those siblings as the alternatives it replaces.

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

Usage Guidelines3/5

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

The phrase 'pre-trade check' implies the moment to use it, and 'in one call' implies it replaces several single-signal calls. But there is no explicit 'use this instead of robinx_verdict + robinx_deployer + robinx_smart_holders' routing and no stated exclusions or preconditions beyond the Robinhood Chain token type.

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

All robinx-mcp 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