Skip to main content
Glama

coinop-mcp

coinop_record

A wallet's public verified record: best score and all-time rank per cabinet, games played, QTR earned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "<wallet>"
    },
    "name": "coinop_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes0x address of the caller's wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It does convey that the record is 'public' and 'verified', implying a permissionless read of validated on-chain data, which is genuinely useful context. It does not say what happens for an unknown or unverified wallet (empty result vs. error) or whether the response is scoped to the caller — meaningful gaps for a no-annotation tool.

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 compact sentence fragment with zero filler, and the key information (whose record and what it contains) is front-loaded. It is arguably over-terse — a leading verb would cost one word and improve scanability — but nothing is wasted.

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?

Because there is no output schema, the description usefully enumerates the returned fields, which is the right compensation. However, for a lookup tool with no annotations, it leaves out error/empty behavior and any guidance on which sibling to use for related data, so it is adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'wallet' parameter is documented as a '0x address', so the schema does the heavy lifting. The description adds only that the wallet is the subject of a public verified record, with no extra format, casing, or checksum guidance beyond the schema — baseline 3 for a one-param tool.

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

Purpose3/5

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

The description names the resource ('a wallet's public verified record') and enumerates its contents (best score, all-time rank per cabinet, games played, QTR earned), so the agent knows what it returns. But it's a noun phrase with no verb, and it never distinguishes itself from adjacent siblings such as coinop_stats, coinop_state, or coinop_rewards, so an agent cannot tell from the text alone which retrieval tool to pick.

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 when-to-use guidance at all — no statement that this is the lookup to call for a single wallet's profile/standing versus the aggregate tools. The only implicit hint is the word 'public', which suggests no auth or ownership is required, but nothing states prerequisites, alternatives, or exclusions.

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.