Skip to main content
Glama

coinop-mcp

coinop_tasks_nonce

EXCHANGE: a one-time nonce + the exact message ('COINOP task::') to sign locally. Every Exchange mutation (task post/claim/submit/accept/reject/cancel, profile) takes a FRESH nonce + signature — nonces are single-use.

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

Input Schema

NameRequiredDescriptionDefault
walletYes0x address of the caller's wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses key traits: one-time nonce, single-use, fresh nonce required per mutation, and the exact message to sign locally. It does not cover expiry, error behavior, or rate limits, but the core behavior is well explained.

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?

The description is two tight sentences. It front-loads the exchange outcome and exact message format, then immediately explains the fresh-nonce requirement for mutations.

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 nonce tool with no annotations or output schema, the description is largely complete: it states what is returned, the exact message format, and the single-use mutation requirement. Minor gaps around expiry or failure modes remain but do not block correct use.

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%, so the wallet parameter is already documented as the caller's 0x address. The description adds meaning by showing that the wallet address is embedded into the signing message as 'COINOP task:<wallet>:<nonce>'.

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 clearly states that the tool exchanges a one-time nonce and exact message for local signing, with the message format 'COINOP task:<wallet>:<nonce>'. It is specific but does not explicitly distinguish itself from sibling nonce tools such as coinop_claim_nonce or coinop_qtr_nonce.

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?

It explains that every Exchange mutation (task post/claim/submit/accept/reject/cancel, profile) takes a fresh nonce plus signature, and that nonces are single-use. This gives clear when-to-use context, though it does not name alternative nonce sources or exclusions.

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.