Skip to main content
Glama

coinop-mcp

coinop_state

Current server-authoritative state of a play session.

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": {
      "sessionToken": "<sessionToken>"
    },
    "name": "coinop_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionTokenYesSession token returned by coinop_insert_coin / coinop_create_match / coinop_join_match (or the latest coinop_heartbeat)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. "Server-authoritative" usefully signals that the returned state overrides any client-side view, but nothing is said about read-only safety, idempotency, whether the token can expire, or what happens on an invalid/expired session token.

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?

One short sentence with no padding or redundancy. It is efficient, though the brevity edges toward under-specification rather than disciplined conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a read tool with no output schema and no annotations, so the description must explain what the returned state contains; it does not. An agent knows only that some session state comes back, not its shape or which fields matter for deciding the next action.

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 description coverage is 100% and the single sessionToken parameter is documented in the schema, including which sibling tools issue it. The description adds no parameter meaning of its own, so the baseline 3 applies.

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?

"Current server-authoritative state of a play session" identifies the resource (play session state) and its freshness/authority, but it is a noun phrase with no verb and no explicit differentiation from close siblings like coinop_match_status or coinop_list_matches. An agent can guess it fetches session state, but not precisely how it differs from the match-status tool.

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 of whether this is for polling during play, for reconnection recovery, or for verifying server truth against a local view. No alternatives are named, despite coinop_match_status and coinop_list_matches plausibly overlapping.

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.