Skip to main content
Glama

One trader

get_trader
Read-onlyIdempotent

One trader: a row per category, rule check, radar with n, stars history, 5 newest trades. <=3 KB.

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": {
      "trader": "<trader>"
    },
    "name": "get_trader"
  }
}

Input Schema

NameRequiredDescriptionDefault
catNo
formatNo
traderYesslug, 0x wallet, 8-hex, Polymarket URL or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add genuine behavioral context beyond that – the <=3 KB response cap and the fixed composition of the return payload – which helps an agent budget context, though the cryptic field labels reduce the value.

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

Conciseness3/5

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

It is extremely short and front-loaded with the resource, with no filler sentences. But the compression goes too far: the comma-separated fragment list reads as shorthand notes rather than a spec, and "radar with n" is not parseable without prior knowledge of the product.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 3 parameters, the description carries the full burden, and it leaves two of three parameters undefined and gives no usage context. It partially sketches the return payload, but an agent could not reliably call this tool with a category filter or choose an output format from this text.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: only 'trader' is documented (slug, 0x wallet, 8-hex, URL or name). Neither 'cat' nor 'format' is explained anywhere – the description never says what a category filter does or that format selects tsv vs json output, so the description entirely fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it returns a single trader and enumerates the payload contents (per-category row, rule check, radar with n, stars history, 5 newest trades), so the resource is clear. However it never states a verb and it never distinguishes itself from the sibling find_traders, and terms like "radar with n" and "rule check" are unexplained jargon an agent cannot interpret confidently.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no mention of when to pick get_trader over find_traders, no prerequisites, no indication of what happens when a slug is ambiguous or a trader is not found. The agent must infer all routing from the tool name alone.

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.

Resources