Skip to main content
Glama
Sign In

robinx-mcp

by io.github.jamhimself
OverviewDiscussionsAdmin

Top trusted deployers

robinx_leaderboard
Read-only

The highest-reputation deployers on Robinhood Chain, ranked: every wallet whose full-history score is >= 70, with launch counts and track record. Costs $0.01 USDC on Base. (paid $0.01, or included in a RobinX plan key — see instructions)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds genuinely non-obvious behavior: the call costs $0.01 USDC on Base or is covered by a RobinX plan key. It stops short of describing result size/limit or caching, which would be useful for an openWorld query.

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 result definition and efficiently sized. The trailing parenthetical repeats the pricing already stated in the prior sentence, a minor redundancy.

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?

For a zero-parameter tool with no output schema, the description conveys what is returned and the payment requirement. It omits practical details like how many deployers come back or whether results are cached, but nothing needed to invoke 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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and the inclusion threshold (>= 70) is stated as a fixed rule rather than a filter argument.

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 resource (highest-reputation deployers on Robinhood Chain), the ranking basis (full-history score >= 70), and the returned fields (launch counts, track record). This distinguishes it from the single-entity sibling robinx_deployer and from the broader robinx_callers/leaderboard-style tools.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance, and no routing to siblings such as robinx_deployer for a single address. Usage is only implied by the leaderboard framing.

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