Skip to main content
Glama

Tradoshi rankings and research

A ranking

get_rankings
Read-onlyIdempotent

A page of the Tradoshi 2027 ranking of trading and investing schools (filter by country or continent) or prop firms (filter by market: futures, forex-cfd, crypto, stocks, by trading platform: ctrader, mt5, match-trader, tradovate…, or by country).

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": {
      "type": "<type>"
    },
    "name": "get_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
limitNo
marketNo
offsetNo
countryNoISO 3166-1 alpha-2 code
platformNoProp firms only: trading platform offered, for example ctrader, mt5, match-trader
continentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 adds that results are paginated ('A page of') and that filter applicability depends on type. It doesn't mention page-size defaults, max limit, or what a ranking entry contains, so the added context is modest.

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?

The core identity ('A page of the Tradoshi 2027 ranking...') is front-loaded, and the parentheticals carry only filter details. It is a single dense sentence that is readable but slightly overloaded with enumerated examples.

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?

With 7 parameters, low schema coverage, and no output schema, the description covers the main risk — passing an incompatible filter for the chosen type. Missing are pagination guidance and any hint of the ranking fields returned, which matters somewhat given there is no output schema.

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 description coverage is only 29%, but the description compensates by clarifying conditional applicability — market and platform apply only to prop_firms, country/continent to schools and country to prop firms — and by giving concrete example values for platform (ctrader, mt5, match-trader, tradovate). limit/offset and the type enum remain unexplained, so it's not a full 5.

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

Purpose5/5

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

The description names a specific verb+resource: it returns 'A page of the Tradoshi 2027 ranking of trading and investing schools... or prop firms', and it immediately identifies the two entity domains. That distinguishes it cleanly from detail siblings like get_school and get_prop_firm, which return a single entity rather than a ranked list.

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

Usage Guidelines4/5

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

It states usage conditions per type — schools are filtered by country or continent, prop firms by market, trading platform, or country — so an agent knows what to pass for each mode. It doesn't explicitly say when to prefer this over search_entities or get_school/get_prop_firm, which keeps it short of a 5.

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.