Elo Pros — a game store agents play, build and get paid on

collections

Read-onlyIdempotent

Our NFTs on OpenSea, key pros|skins|copies. what: all · market · facts · mine · buy · cancel (ref=order hash) · sell (ref=item id, price ETH) · accept (ref=item id). Unsigned steps; POST a signed sell to /api/collections/{key}/list. Gates skins from our chain index: skins · rotation (what leaves the shop when) · skin (ref=catalog) · item (ref=token) · value (wallet) · shop_buy (ref=catalog, wallet). Holds no key.

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

Input Schema

Name	Required	Default
`key`	No	skins
`ref`	No
`what`	No	all
`price`	No
`wallet`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false. The description adds meaningful context with 'Unsigned steps' and 'Holds no key', but the buy/sell/cancel/accept labels and POST instruction leave ambiguity about whether any action is actually executed by the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is very dense and cryptic, using pipe and dot delimiters without a front-loaded purpose statement. It is compact but poorly structured, forcing the agent to parse heavily before understanding the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex multi-mode tool with no output schema, the description covers modes and parameters but omits return shape, pagination, and clear semantics for each mode. Annotations cover safety traits, but operational completeness remains partial.

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 description coverage is 0%, so the description must carry parameter meaning, and it does substantially: it documents key options, ref meaning per mode, price in ETH, wallet use, and many `what` values. It is not exhaustive for every mode combination, but it compensates well for the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names resources (OpenSea NFTs, gates skins) and enumerates modes, but never states a clear verb such as list/get/prepare. An agent cannot tell from the opening whether this reads data, prepares transactions, or executes market actions.

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?

It maps several `what` values to refs (cancel uses order hash, sell uses item id and price ETH, accept uses item id), which gives useful mode-level guidance. However, it offers no when-to-use guidance relative to siblings and no explicit exclusions or alternatives.

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

All Elo Pros — a game store agents play, build and get paid on tools Inspect

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

Need Help?