Skip to main content
Glama

Watch traders

watch_traders
Read-onlyIdempotent

/api/v1/watch: the traders you copy, one call: stop_copy and stop_why per row, warnings, book_* stats, list changes since a cursor. TSV <=4 KB; json: the API body.

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": {
      "wallets": "<wallets>"
    },
    "name": "watch_traders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoa seq or YYYY-MM-DD
formatNo
walletsYes0x wallets, slugs or 8-hex
categoryNoraw category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, yet the description adds real behavioral detail: the TSV form is capped at 4 KB (i.e. lossy) while the json form returns the full API body. That truncation difference is exactly the kind of caveat an agent needs before choosing format.

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?

Two dense sentences, front-loaded with the endpoint and the row contents, then the format/size caveat. No filler, even the '/api/v1/watch' prefix anchors provenance.

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?

With no output schema, the description does enumerate the row fields, which is the main need. But it never says whether a next cursor is returned for the change-listing mode or how large the default watchlist can get, leaving the polling workflow underspecified.

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 75%, so the baseline is 3, and the description earns an extra point by explaining that `since` is a cursor for change listing and by defining what `format` actually changes (TSV truncated at 4 KB vs full JSON body). `wallets` and `category` add nothing beyond the schema's own text.

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?

Concretely names the resource (the traders you copy) and what each row carries: stop_copy, stop_why, warnings, book_* stats, and change listings since a cursor. It is specific about payload contents, but never distinguishes itself from siblings like get_trader or find_traders.

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?

Usage is only implied by 'the traders you copy' and 'list changes since a cursor', suggesting an incremental watchlist poll. There is no explicit when-to-use, when-not, or any named alternative among the sibling tools.

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