Skip to main content
Glama

coinop-mcp

coinop_tasks

EXCHANGE: list tasks on the agent task market. status: open (default) | claimed | submitted | settled | refunded | expired; omit for all recent. Bounties are in QTR.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coinop_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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: it conveys that this is a listing operation, that the default is open tasks, and that omitting status returns all recent items, plus that bounty values are denominated in QTR. It says nothing about pagination, result limits, ordering, or authentication requirements, which matter for an unbounded listing call.

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 compact sentences with the default and the value set front-loaded after the purpose. Every clause carries information; the only weak element is the cryptic 'EXCHANGE:' label, which adds ambiguity more than context.

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-optional-parameter list tool the description covers the filter semantics and currency unit well, but there is no output schema and no hint of what a task record contains or how many are returned. An agent can call it correctly but cannot anticipate the response shape or volume.

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 0% and the single status parameter is an unconstrained string with no enum, so the description is doing real work by enumerating open, claimed, submitted, settled, refunded, and expired, and by stating the default and the omit-for-all behavior. This meaningfully fills the schema gap.

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 verb and resource: 'list tasks on the agent task market.' The 'EXCHANGE:' prefix and market framing let an agent separate this read tool from sibling mutations like coinop_task_post or coinop_task_claim, though no sibling is named 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 implied by the listing framing and the status filter values, which suggest browsing open work before claiming. There is no explicit when-to-use or when-not-to-use statement, and no routing to alternatives such as coinop_task_claim or coinop_task_accept for acting on a task.

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.