YorkerAPI

Leaders

get_leaders

Read-onlyIdempotent

Use for the leaders in a stat (runs, batting_average, strike_rate, sixes, wickets, economy, bowling_average) in a competition, season or format. Rate stats need min_balls faced or bowled (default 120). Costs 5 credits.

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": {
      "stat": "<stat>"
    },
    "name": "get_leaders"
  }
}

Input Schema

Name	Required	Description
`stat`	Yes
`limit`	No
`format`	No
`gender`	No
`league`	No	League. Defaults to cricket. One of: cricket, test, odi, t20i, ipl, bbl, psl, cpl, blast, hundred, sa20, ilt20, county, wbbl, wpl, hundred_women.
`season`	No	Season: a year (2024) or a split season (2024/25).
`min_balls`	No
`competition`	No	Competition key from list_competitions (ipl, bbl, test, odi, t20i, ...).

Output Schema

Name	Required	Description	Default
`stat`	Yes
`count`	Yes
`leaders`	Yes
`min_balls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/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 genuinely non-obvious behavior beyond that: rate stats silently apply a min_balls threshold defaulting to 120, and the call costs 5 credits. Missing items like result ordering or truncation behavior keep it at 4.

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 with no filler: purpose and scope first, then the rate-stat threshold and cost. Every clause carries information an agent needs before calling.

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 an output schema present, return values need no explanation, and the description covers scope, the stat enum, the qualifying threshold, and cost. Gaps remain around default limit/pagination and the effect of omitting league and gender, but the essentials for a correct call are 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 description coverage is only 38%, so the description must carry weight. It usefully supplies the min_balls default (120) that the schema omits, and confirms which dimensions scope the leaderboard. However, it says nothing about limit, gender, or the league default semantics, leaving several parameters unexplained in both places.

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 ('leaders in a stat') and enumerates the seven valid stats along with the scoping dimensions (competition, season, format). An agent can immediately tell this returns leaderboards rather than match or player detail, though it never explicitly contrasts itself with siblings like get_player_stats.

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?

'Use for the leaders in a stat ... in a competition, season or format' gives clear conditions for selecting this tool over match-level tools. It also flags that rate stats require min_balls, which is a usage constraint. It stops short of naming an alternative for raw per-player stat lookup, so it falls 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.

All YorkerAPI tools Inspect

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

Need Help?