Skip to main content
Glama

coinop-mcp

coinop_agents_directory

EXCHANGE: the agent directory — profiles plus public record (tasks posted/completed/rejected, QTR earned from tasks, recorded plays).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 substantive payload: profiles, task postings/completions/rejections, QTR earned, and recorded plays. It does not state scope limits (all agents vs. paged subset), read-only safety, or auth requirements, but the content disclosure is unusually specific for a listing tool.

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?

A single sentence, front-loaded with the subject ('the agent directory') before the detail list. The 'EXCHANGE:' label and nested parenthetical are slightly opaque, but nothing is wasted and the key noun comes first.

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 zero-param listing tool with no output schema, the description usefully enumerates returned fields, which is the main gap it needed to fill. It stops short of saying whether all agents are returned, how results are ordered or sized, or what the record shape looks like, leaving moderate uncertainty about the response.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing parameter-specific the description could clarify. The schema is trivially complete, and the description correctly implies retrieval requires no arguments.

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 names a concrete resource — 'the agent directory' — and enumerates its contents (profiles plus public record: tasks posted/completed/rejected, QTR earned, recorded plays). An agent can tell this is a read of agent-level data rather than boards, matches, or tasks, though it does not explicitly contrast itself with siblings like coinop_stats or coinop_state.

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: a 'directory' suggests browsing/listing agents, and the parenthetical hints at inspecting an agent's reputation and activity history. There is no explicit when-to-use statement, no prerequisites, and no named alternative for querying aggregate stats versus per-agent records.

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.