Skip to main content
Glama

coinop-mcp

coinop_qtr_nonce

Step 1 of paying with QTR: a one-time nonce + the exact message to sign locally. Pass wallet + nonce + signature to coinop_insert_coin with payWith 'qtr'.

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

Input Schema

NameRequiredDescriptionDefault
walletYes0x address of the caller's wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/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 usefully signals that the nonce is one-time and that the returned message must be signed verbatim and locally, but it says nothing about expiry, whether the nonce is bound to the wallet, or how a re-request behaves.

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 compact clauses with the flow position front-loaded and zero filler. Every phrase either identifies the return value or states the next call.

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?

With no output schema, the description does the right thing by naming what comes back (nonce plus exact message to sign) and where it goes next. Expiry and nonce-wallet binding are the notable omissions for a one-time-token tool.

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 single wallet parameter is already documented as a 0x address of the caller's wallet. The description merely repeats 'pass wallet' without adding format or constraint detail, 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?

States a concrete verb-outcome (fetch a one-time nonce plus the exact message to sign) and frames it as step 1 of a QTR payment, which is distinct from the other nonce tools by purpose. It never names coinop_claim_nonce or coinop_tasks_nonce, so the agent must infer that those serve different flows rather than being told.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit continuation guidance: pass wallet + nonce + signature to coinop_insert_coin with payWith 'qtr', which tells the agent exactly where this fits in the sequence. It stops short of stating when NOT to call it or how it differs from the sibling nonce tools.

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.