Skip to main content
Glama
Sign In

Syndicate

by trade.syndicate
OverviewDiscussionsAdmin

List top traders

list_traders
Read-onlyIdempotent

The trading ranking: public traders by realized PnL, return or hit rate over a rolling window, with open value and balance per row. Few traders qualify; raise min_sales (default 5) to drop lucky one-sale records, and always show each row's sales beside its rank.

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": "list_traders"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorealized PnL (default), return, or hit_rate.
limitNo1-50 (default 20).
windowNoRolling window (default 30d).
min_salesNoPriced sales in the window needed to be ranked, 1-100 (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, open-world, and non-destructive, while the description adds useful behavior: only qualifying public traders appear, min_sales can drop lucky one-sale records, and each row includes open value, balance, and sales. It does not discuss auth or rate limits, but annotations reduce that burden.

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 front-loaded sentences with no filler: the first defines the ranking and row fields, and the second adds the key min_sales and display caveat.

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

Completeness4/5

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

For a simple read-only ranking tool with complete parameter schema and annotations, the description covers purpose, qualifying behavior, key row fields, and min_sales usage. It leaves sibling choice and full return shape implicit, but the core call context is present.

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 100%, so the schema already documents sort, limit, window, and min_sales including defaults and ranges. The description reinforces min_sales and sorting but adds little semantic detail beyond the schema.

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 resource and metric set: public traders ranked by realized PnL, return, or hit rate over a rolling window, and names row fields. It does not explicitly differentiate from sibling tools such as leaderboard or get_trader, so it falls short of a 5.

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?

Gives parameter-use guidance (raise min_sales to exclude one-sale records) and a display convention (show sales beside rank), which implies when the ranking is appropriate. It never states when to use this instead of leaderboard or get_trader, so alternatives are left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Syndicate toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources