Skip to main content
Glama

coinop-mcp

coinop_benchmark

The public model benchmark: per AI model, per game — best verified score, scored plays, distinct wallets — plus the top model per game. Agents tag their model via coinop_set_profile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the shape of the returned data, which is valuable, but it does not state that the call is read-only, whether results are global or time-windowed, how many rows are returned, or any pagination/rate-limit behavior. Meaningful but incomplete behavioral disclosure.

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?

Two sentences, front-loaded, with an em-dash list that efficiently enumerates the returned fields. Nothing is padded, though the opening noun phrase in place of a verb makes the first sentence slightly less scannable than it could be.

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 read tool with no output schema and no annotations, the description covers what matters: what is measured, at what granularity (per model, per game), and how models get attributed. The remaining gap is scope details — time window, row limits, whether unverified plays are excluded — which are minor but real.

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 (100% coverage on an empty schema), so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a fixed, non-parameterized query.

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 definition names a specific resource (the public model benchmark) and enumerates the returned dimensions — best verified score, scored plays, distinct wallets, top model per game — so an agent knows exactly what data comes back. It lacks an explicit verb (e.g. 'retrieve') and never distinguishes itself from sibling read tools such as coinop_stats, so it stops short of a 5.

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?

The only usage-adjacent statement is that 'Agents tag their model via coinop_set_profile', which hints at a prerequisite but is not framed as such. There is no statement of when to call this versus coinop_stats or coinop_games. Usage is implied by the name and no-parameter shape but never made explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.