Skip to main content
Glama
Sign In

robinx-mcp

by io.github.jamhimself
OverviewDiscussionsAdmin

Identify a chart screenshot

robinx_identify
Read-only

Paste a crypto price-chart SCREENSHOT and get back which Robinhood Chain token it shows. Vision reads the printed ticker and last price, then matches against live per-token prices and volume rank (a visible ticker wins outright; otherwise a ±20% price band ranked by closeness and volume, with a confidence score and alternates). Charts from Solana/Base/Ethereum are detected and resolved cross-chain via DexScreener rather than force-matched against RH-chain tokens. Pass image as base64 (raw or data: URL). Free 5/day per IP, then $0.02 USDC on Base.

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": {
      "image": "<image>"
    },
    "name": "robinx_identify"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesbase64-encoded chart screenshot (raw base64 or a data:image/png;base64,… URL)
media_typeNoimage/png (default), image/jpeg, image/webp, or image/gif

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 declare readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds significant behavioral context: matching algorithm details (exact ticker or ±20% band with volume rank), cross-chain resolution via DexScreener, and pricing (5 free/day then $0.02 USDC). No contradiction.

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 somewhat long but well-structured and front-loaded with the main action. Every sentence adds value. Could be slightly more concise, but no wasted words. Effective communication.

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?

Given the complexity (image recognition, live matching, cross-chain), the description is complete: explains matching logic, confidence score, alternates, and pricing. No output schema but description gives adequate output hints.

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%. The description adds extra meaning for the 'image' parameter: 'Pass image as base64 (raw or data: URL)', clarifying the format beyond the schema. For 'media_type', no additional meaning beyond schema. Baseline 3 raised to 4 for image clarification.

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's purpose: paste a crypto price-chart screenshot and identify which Robinhood Chain token it shows. It specifies the method (Vision reads ticker/price, matches against live data) and differentiates from siblings by being the only image identification tool.

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?

The description provides explicit guidance on when to use (screenshot) and how (pass base64). It also mentions handling of charts from other chains (detects and resolves cross-chain). However, it does not explicitly state when not to use or suggest alternatives, but given siblings, no alternative exists.

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