YorkerAPI

Player stats

get_player_stats

Read-onlyIdempotent

Use for a player's batting and bowling split by season, competition, phase of the innings (powerplay, middle, death) or format, optionally inside one format, competition or season. 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": {
      "player_id": "<player_id>"
    },
    "name": "get_player_stats"
  }
}

Input Schema

Name	Required	Description
`by`	No	How to split (default format).
`format`	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).
`player_id`	Yes	Player id from search_players.
`competition`	No	Competition key from list_competitions (ipl, bbl, test, odi, t20i, ...).

Output Schema

Name	Required	Description	Default
`name`	Yes
`count`	Yes
`batting`	Yes
`bowling`	Yes
`player_id`	Yes
`grouped_by`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description's distinctive addition is the cost disclosure ('Costs 5 credits'), which matters for a metered API. It says nothing about result limits, empty-result behavior for players with no data, or rate/credit consumption per call shape, so it adds only modest context.

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?

Two short sentences, front-loaded with the purpose, with the credit cost appended as a compact operational note. Dense but every clause carries information; minor cost is that the single long first sentence packs splits and filters together.

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 annotations cover the safety profile, so the description only needs purpose, scoping, and cost — all of which are provided. The one gap is the absence of any note on what happens when a player lacks coverage for a given league/season combination.

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 83%, so the baseline is 3; the description earns above that by making the crucial split-vs-filter distinction ('split by ... optionally inside one format, competition or season') and by naming the phase values (powerplay, middle, death) that the schema's `by` enum doesn't spell out. It still leaves the interaction between `by` and the filter params implicit.

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 verb-plus-resource ('a player's batting and bowling split') and enumerates the split dimensions (season, competition, phase, format). An agent can distinguish this from get_player (bio) and get_player_matches by the split-by framing, though no sibling is named explicitly.

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?

Opens with 'Use for', giving clear context, and the phrase 'optionally inside one format, competition or season' tells the agent the tool works both aggregated and filtered. No when-not guidance or named alternative (e.g. get_player, get_matchup) is given, so it stops short of full routing guidance.

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?