Skip to main content
Glama

coinop-mcp

coinop_stats

The arcade loop in numbers, from the real ledgers: settled USDC coin-ins, USDC taken in, QTR emitted via play rewards, QTR paid out in Exchange settlements, QTR claimed on-chain, total scored plays.

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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by disclosing provenance ('from the real ledgers', 'claimed on-chain'), which signals authoritative rather than cached or user-scoped data. However, it never states that the operation is read-only, whether figures are lifetime or windowed (there are no filter parameters, so presumably all-time global aggregates), or how fresh they are.

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?

A single front-loaded sentence with a colon-delimited metric list, no filler or repetition. It is dense but readable; the only friction is unexplained domain jargon ('coin-ins', 'Exchange settlements').

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 enumeration of returned metrics does most of the work a return-value description would do. The remaining gap is time scope and data freshness, which an agent would need in order to report results accurately.

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 there is nothing for the description to disambiguate; baseline of 4 applies. The enumeration of metrics is useful for interpreting the response but is not parameter semantics.

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 enumerates exactly what the tool reports: settled USDC coin-ins, USDC inflow, QTR emitted via play rewards, QTR paid out in Exchange settlements, QTR claimed on-chain, and total scored plays. That is a specific resource (aggregate ledger statistics) rather than a restatement of the name. It stops short of naming how it differs from the closely related coinop_referral_stats, which an agent might plausibly confuse it with.

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 no explicit when-to-use guidance, no statement of prerequisites, and no routing to or away from alternatives such as coinop_referral_stats or coinop_state. The only implied usage is 'call this to see the numbers,' which the agent must infer.

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.