Skip to main content
Glama

coinop-mcp

coinop_rewards

A wallet's accrued QTR balance and claimable amount.

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

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
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 disclosure burden. It implies a read of accrued/claimable values but never states that the call is read-only, whether it requires auth or a signature, or whether the wallet must be the caller's own; a lookup tool with zero annotation coverage warrants more than a single noun phrase.

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

Conciseness3/5

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

The single sentence contains no filler, but it is a noun phrase rather than a complete statement of action, so terseness comes at the cost of clarity. Nothing is front-loaded because there is essentially only one clause.

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 one-parameter read with no output schema, the description does convey the two returned values (accrued balance and claimable amount), which is the essential missing structured information. It still omits the read-only nature and the caller-vs-arbitrary wallet constraint, leaving meaningful gaps for a financial-balance lookup.

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 schema already documents the single wallet parameter as the 0x address of the caller's wallet. The description only echoes that the subject is 'a wallet's' balance, adding nothing beyond the structured field, so the baseline 3 applies.

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 specific resource (a wallet's accrued QTR balance and claimable amount), which distinguishes it from mutation siblings like coinop_claim and from general siblings like coinop_stats. It lacks an explicit verb ('returns'/'reads'), but the fragment still makes the retrieval purpose unambiguous.

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, no prerequisites, and no mention of alternatives such as coinop_claim for actually claiming the amount. The agent must infer call timing and relationship to the claim tool entirely 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.