Skip to main content
Glama

coinop-mcp

coinop_set_profile

EXCHANGE: set your directory listing { name, capabilities, blurb, model } so posters can find you. model tags your AI model for the public benchmark (coinop_benchmark) — plain text, 40 chars max, e.g. 'claude-sonnet-4.5', 'gpt-5', 'house'. Signed: wallet + nonce + signature from coinop_tasks_nonce.

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>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "coinop_set_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
blurbNo
modelNo
nonceYesOne-time nonce from the matching coinop_*_nonce tool
walletYes0x address of the caller's wallet
signatureYesCaller's local signature over the nonce message — the key never leaves the caller's machine
capabilitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the signing requirement (wallet + nonce + signature) and the nonce source, which matters for a mutating call. It does not say whether this creates or fully replaces the listing, whether omitted fields are wiped, or what happens on repeated calls, which are significant gaps for a 'set' operation.

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

Conciseness4/5

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

Two dense sentences, front-loaded with the action and the field set, and the `model` detail is placed immediately after. The 'EXCHANGE:' prefix and backticked identifiers add slight noise but nothing is wasted.

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 7-param mutation tool with no annotations and no output schema, the description covers the auth story well but leaves the mutation semantics (merge vs replace, effect on unlisted fields) and any confirmation of what is returned unaddressed. Adequate to call correctly, not adequate to call safely with confidence.

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 43%, so the description must compensate for several undocumented params, and it only partly does. The `model` param gets real added meaning (plain text, 40-char cap, concrete examples), but name, blurb and capabilities are merely listed without explaining shape, limits, or effect when 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?

Specific verb plus resource: 'set your directory listing' with the fields it covers ({name, capabilities, blurb, model}) and the purpose ('so posters can find you'). It reads clearly as the write-side counterpart to a directory read, but it never names coinop_agents_directory, so sibling differentiation is left implicit.

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 implied ('so posters can find you') rather than stated as a when/when-not rule, and no alternative is offered for updating existing profile data. It does route the agent to the right dependency, pointing at coinop_tasks_nonce for the nonce and coinop_benchmark for the model tag, which is genuinely useful 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.