Skip to main content
Glama

coinop-mcp

coinop_referral_stats

REFERRALS: a wallet's referral tallies — code, agents referred, qualified, and total referral QTR earned. Public.

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

Input Schema

NameRequiredDescriptionDefault
walletYes0x address of the caller's wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose that the endpoint is public (no auth) and that it returns tallies rather than performing a mutation, which is genuine added context. It says nothing about behavior for a wallet with no referrals (zeros vs. error), whether counts are lifetime or windowed, or any chain/token scoping for the QTR figure.

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?

One sentence, front-loaded with the resource category, and every clause carries information — the returned field list in particular earns its place because there is no output schema. No filler.

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 simple one-parameter read with no output schema, the description covers the essential return shape (code, referred, qualified, QTR total), which is exactly what an agent needs. The residual gaps — empty-state behavior and time scope of the tallies — are modest but real for a stats endpoint.

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?

There is a single required parameter with 100% schema description coverage ('0x address of the caller's wallet'), so the schema already does the work; the description's phrase 'a wallet's' merely restates it. It adds no format guidance, no note on whether the wallet must match an authenticated caller despite the endpoint being public.

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 resource (a wallet's referral tallies) and enumerates what is returned: code, agents referred, qualified, total referral QTR earned. The 'REFERRALS:' prefix plus the field list separates it from coinop_referral_code and coinop_stats well enough, though it never names those siblings 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?

Usage is only implied — an agent can infer this is the read for a wallet's referral totals, but there is no explicit when-to-use or when-not-to-use guidance in relation to coinop_referral_code (code retrieval/creation) or coinop_stats. 'Public' hints at no auth requirement rather than describing invocation context.

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.