YorkerAPI

Matches

get_matches

Read-onlyIdempotent

Use for results: matches newest first with both scores, toss, result and margin. Filter by competition, season, team, opponent, venue, date or a date range. Costs 2 credits.

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

Input Schema

Name	Required	Description
`to`	No	Start date on or before (YYYY-MM-DD).
`date`	No	A day the match was played (YYYY-MM-DD); multi-day matches match on any day.
`from`	No	Start date on or after (YYYY-MM-DD).
`limit`	No	Max matches (default 50).
`venue`	No	Part of the ground or city name.
`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.
`offset`	No
`season`	No	Season: a year (2024) or a split season (2024/25); a year also finds the split season that starts in it.
`team_id`	No	Team id from list_teams.
`competition`	No	Competition key from list_competitions (ipl, bbl, psl, blast, hundred, county, test, odi, t20i, ...).
`opponent_id`	No	Only matches against this team too.

Output Schema

Name	Required	Description	Default
`count`	Yes
`matches`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds two genuinely non-structured facts: default ordering (newest first) and cost (2 credits). It says nothing about pagination limits or result volume, which matters for a 13-parameter list endpoint.

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?

Three short sentences, front-loaded with the use case, then output shape, then filters, then cost. No wasted words; the only nit is the clipped "Use for results:" phrasing and the trailing cost sentence arriving after the filter list.

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 13-parameter list tool with an output schema and rich annotations, the description covers purpose, ordering, filter axes and credit cost. Return value detail is rightly delegated to the output schema; only pagination behavior and single-match alternatives are unaddressed.

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 77%, so the baseline is 3. The description enumerates the filterable dimensions (competition, season, team, opponent, venue, date, date range), which reinforces the schema but adds no syntax, cross-parameter interaction, or defaults beyond what the properties already document.

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?

Names a specific resource (matches) and states the shape of the result: newest first, with both scores, toss, result and margin. That is far more than a restatement of the title, but it never differentiates itself from siblings such as get_match or get_player_matches by name.

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?

"Use for results" plus the enumerated filter axes implies when this tool is appropriate, but there is no explicit when-not condition and no named alternative for retrieving a single match. Usage is suggested rather than routed.

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?