Skip to main content
Glama

coinop-mcp

coinop_prizes

The weekly USDC prize pool: current pool, per-cabinet shares, this week's leaders, and payouts already made. Each cabinet's best verified score of the week (Mon 00:00 ET) takes its share, paid automatically in USDC.

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

Input Schema

NameRequiredDescriptionDefault
weekNoOptional past week key YYYY-MM-DD (a Monday)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers substantive domain behavior: settlement is weekly, the week boundary is Monday 00:00 ET, each cabinet's best verified score earns a proportional share, and payouts happen automatically in USDC. It stops short of stating that the call is a read-only query or how incomplete/settling weeks behave, which keeps it out of the top band.

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?

Two sentences with no filler: the first front-loads the returned data set, the second explains the payout rule and timing. Every phrase contributes either to scope or to mechanics.

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 query tool with no annotations and no output schema, the description covers the resource, the computation rule, and payout timing well enough to call correctly. Remaining gaps are minor: no explicit read-only statement, no guidance on a week with no data, and no mention of whether pending versus completed payouts are both included.

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?

Schema coverage is 100% for the single optional week parameter, so baseline expectations are modest, but the description adds real meaning: the week is anchored to Monday 00:00 ET, clarifying what a valid week key represents. It still does not explicitly say the current week is returned when week is omitted.

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 names a concrete resource ("weekly USDC prize pool") and enumerates its four component views: current pool, per-cabinet shares, this week's leaders, and completed payouts. An agent can tell it fetches prize/payout data rather than match state or generic rewards, though it never uses an explicit retrieval verb and offers no direct differentiation from the sibling coinop_rewards.

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?

Usage is only implied — the mention of "this week's leaders" and the schema's "optional past week" suggests querying the current or a historical week, but there is no statement of when to pick this over coinop_rewards, coinop_stats, or coinop_claim. No prerequisites or exclusions are given, leaving the agent to infer selection.

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.