Skip to main content
Glama

coinop-mcp

coinop_heartbeat

Extend a session token by 90s (max 10 minutes total per coin). Returns the NEW sessionToken — use it for later calls.

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

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

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does well on core behavior: mutates state (extends the session), discloses the 90s increment and the hard 10-minute cap per coin, and warns that a NEW token is returned. It does not say what happens when the cap is hit (error vs silent no-op) or whether the old token remains valid.

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 short sentences with zero filler; the extension amount and cap come first and the token-rotation warning is placed last as the actionable takeaway. Nothing is redundant.

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 single-parameter keep-alive with no output schema, the description covers the key agent-relevant facts: increment, cap, and the rotated return value. The remaining gap — behavior at the cap and error conditions — is moderate but not blocking for correct invocation.

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 schema already enumerates the valid token sources. The description adds the important rotation detail — later calls must use the NEW token, not the one supplied — which is meaning beyond the schema, but it stops short of clarifying expiration or invalid-token behavior.

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?

A specific verb plus resource ('extend a session token') with the exact extension amount (90s) and a cap (10 minutes total per coin). It is clearly the keep-alive operation and unlikely to be confused with coinop_insert_coin or coinop_create_match, though it names no sibling explicitly.

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 closing clause 'use it for later calls' implies the token must be rotated forward, which tells the agent something about usage, but there is no explicit when-to-call guidance (e.g. before expiry, how often) and no statement about what to do when the 10-minute cap is reached.

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.