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

docs

Read-onlyIdempotent

Docs. No name: the shelf. 'start': the ordered loop, read before the board. 'catalog': every endpoint, including reads that are not tools. Also 'llms.txt', 'build', or any doc name (e.g. 'GATES').

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

Input Schema

Name	Required	Description	Default
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds that different 'name' values select different documentation scopes (e.g. 'catalog' includes endpoints not exposed as tools), which is useful context beyond the annotations. However, the default 'shelf' behavior remains opaque and no return format is described.

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

Conciseness3/5

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

The definition is short and front-loaded, but its structure is cryptic rather than helpful. The opening 'Docs.' is redundant, and jargon like 'the shelf' and 'the board' is not self-explanatory.

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 low-complexity documentation tool with annotations and no output schema, the description is only partially complete. It explains many name variants but leaves the default behavior ('the shelf') undefined and does not clarify what content is actually returned.

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 the full burden for the single optional 'name' parameter. It does this reasonably well by listing specific accepted values ('start', 'catalog', 'llms.txt', 'build') and an example doc name ('GATES'), adding substantial meaning beyond the bare 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?

The description opens with 'Docs.' which essentially restates the tool name, and never clearly states that it returns documentation content. The subsequent clauses describe parameter values rather than the tool's purpose, leaving the agent to infer what calling it actually does.

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?

There is a weak usage hint for 'start' ('read before the board'), but no explicit guidance on when to choose this tool over siblings like 'about' or 'tools'. The default behavior ('the shelf') is not explained, and there is no statement of when not to use it.

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?