Skip to main content
Glama

coinop-mcp

coinop_games

List the COINOP arcade catalog: games, rules, actions, prices, rewards, boards.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/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 implies a read-only listing but never states that it has no side effects, requires no authentication, is paginated or unpaginated, or roughly how large the response is. The category enumeration is the only real content signal.

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

Conciseness5/5

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

A single front-loaded sentence with the verb and resource first and the catalog contents following. No filler, no restatement of the tool name, nothing that could be cut without losing information.

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 zero-argument listing tool with no annotations and no output schema, the description should at minimum sketch what comes back or in what shape. The category list partially does this, but an agent still cannot predict the response structure, ordering, or whether the catalog is filtered by any implicit state.

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 at the argument level. The baseline of 4 applies with no schema gaps to compensate for.

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?

States a specific verb ('List') and a specific resource ('the COINOP arcade catalog'), then enumerates the domains it covers. An agent can tell this is a read-only discovery/index tool, but the description never distinguishes it explicitly from siblings like coinop_rewards, coinop_prizes, or coinop_tasks, which appear to expose subsets of the same catalog.

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 'catalog' framing implies this is an entry-point/discovery call before calling more specific sibling tools, but that is never stated. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the relationship to the ~30 siblings on its own.

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.