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

store

Read-onlyIdempotent

The store: our hand-picked, open-source games plus community games their developers list themselves. what:

'shelf' (default) every title, trimmed: what it is, its band, whether it
        is playable, which coins it pays or charges.
'title' ONE title in full (needs slug): about, media, build record, the
        economy disclosure, its ticket.
'ticket' a title's copy (needs slug): price, contract, open rails; with
        `wallet`, how many copies that wallet holds.
'items' the items `wallet` holds (needs wallet); `slug` keeps one title's.
'reviews' one title's reviews + summary (needs slug).
'achievements' one title's badges (needs slug), or what `wallet` earned
        across titles. Read each badge's evidence kind: 'onchain' you can
        recompute off a public node, 'replay' is a function of a round
        file, 'attested' is a server's signature, never a fact.
        `earned: null` means WE COULD NOT CHECK. No badge pays or gates money.
'log'   every curation act, newest first, signed (EIP-191).
'desk'  what the curation desk can do now, and whether `wallet` may act.
'prepare' a keeper's dry run for one edit (needs slug): the refusals and
        the text to sign. `fields` for a save, none for a revert.
'live'  who is on a title's shards now, humans and agents apart (needs
        slug). Unknown is null, never 0.
'leaderboard' a title's boards (needs slug), the live wipe and closed ones.

Two lanes. Our own games are placed by hand, alphabetical inside a band;
placement is not for sale. Community games (`community: true`) list with
one signature and reach the shelves only by what they actually sold
through their sale split (GET /api/store/rank, recomputable). Nobody can
pay for a slot in either lane.

No number on a card is money: price, supply, FDV, TVL and holders are
eth_calls, read with wire('tape') and wire('pools'). Writing the catalog is
a keeper's signed act on plain HTTP; nothing here holds a key, and
'prepare' changes nothing.

Input Schema

TableJSON Schema

Name	Required	Default
`slug`	No
`what`	No	shelf
`fields`	No
`wallet`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds rich behavioral context beyond annotations: it clarifies that 'prepare' is a dry run and changes nothing, that 'log' is signed (EIP-191), that 'earned: null' means uncheckable, that no badge pays or gates money, and that no number on a card is money. It also emphasizes that nothing here holds a key, reinforcing the read-only nature.

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 but well-structured with bullet points for each mode, making it scannable. It front-loads the overall purpose and then dives into modes and lanes. While every sentence provides value, the length could be trimmed slightly without losing essential information.

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 tool's complexity (11 modes, 4 parameters, no output schema), the description is thorough: it covers each mode's return content, the two-lane model, safety notes, and the meaning of special values like `earned: null`. An agent would have enough context to invoke it correctly without additional documentation.

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?

With 0% schema description coverage, the description compensates well by explaining the `what` modes and their required parameters (`slug`, `wallet`), the default of 'shelf', and the role of `fields` for saves vs. reverts. It doesn't specify formats for `slug` or `wallet`, but the meaning and usage are clear from context.

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?

The description clearly identifies the tool as a store catalog explorer with multiple query modes (shelf, title, ticket, etc.). It distinguishes between internal and community lanes and hints at sibling tools like wire. However, the multi-purpose nature and the generic name 'store' slightly dilute the clarity compared to a single verb+resource 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?

For each `what` mode, the description states what is returned and what parameters are needed (e.g., 'needs slug'). It also explains the two lanes and that placement is not for sale. It does not explicitly mention when to use this tool versus siblings like `about` or `docs`, but the context is clear enough for an agent to select the right mode.

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?