YorkerAPI

Venue

get_venue

Read-onlyIdempotent

Use for how a ground plays, by format: average first- and second-innings totals, how often the side batting first wins, how often the toss winner wins and what captains choose, and draws. Match by part of the ground or city name. 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": {
      "venue": "<venue>"
    },
    "name": "get_venue"
  }
}

Input Schema

Name	Required	Description
`since`	No	Only matches from this date (YYYY-MM-DD).
`venue`	Yes	Part of the ground or city, e.g. "wankhede" or "adelaide".
`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.
`competition`	No	Competition key from list_competitions (ipl, bbl, test, odi, t20i, ...).

Output Schema

Name	Required	Description	Default
`note`	Yes
`count`	Yes
`venues`	Yes
`by_format`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely useful behavioural fact not in the annotations — the call costs 5 credits — which lets an agent weigh whether to make the call. It does not discuss result size or pagination, but with annotations and an output schema that gap is minor.

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 sentences, purpose first, with the matching hint and credit cost trailing. The metric enumeration is longer than strictly necessary but each listed metric tells the agent something about the return shape, so little is wasted. Tight and front-loaded.

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

Completeness5/5

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

For a 5-parameter read tool with an output schema and full annotation coverage, the description supplies the essential extras: what dimensions of ground behaviour are returned, how to match the venue string, and the credit cost. Remaining gaps (league vs competition, since filter) are documented in the schema, so nothing an agent needs to call it correctly is missing.

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?

With 80% schema description coverage, the baseline is 3; the description reinforces venue matching ('part of the ground or city name') and the 'by format' dimension, which is modest added value. It does not clarify the potentially confusing overlap between the 'league' and 'competition' parameters, nor does it mention the 'since' date filter, so it leaves real ambiguity unresolved.

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?

Names a specific resource (venue/ground behaviour) and enumerates exactly what it returns: first- and second-innings averages, win rates batting first, toss-winner conversion and captain choices, draws. This is clearly a ground-level analytics lookup, distinct from sibling tools like get_match or get_matches, so an agent can select it without opening the schema.

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?

The opening 'Use for how a ground plays, by format' gives a clear usage context and the format dimension is signposted. It also explains how to supply the venue argument ('part of the ground or city name'). It stops short of naming an alternative or an exclusion case, so it is a strong 4 rather than 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?