Skip to main content
Glama
Sign In

YorkerAPI

by io.github.noahowsh
OverviewDiscussionsAdmin

List teams

list_teams
Read-onlyIdempotent

Use for team ids: international sides and franchises, most matches first. Women's sides end in -women (india-women). A renamed side lists its current id in now_plays_as, and filtering on either finds both. Filter by competition, season, gender or part of a name. Costs 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
genderNo
leagueNoLeague. Defaults to cricket. One of: cricket, test, odi, t20i, ipl, bbl, psl, cpl, blast, hundred, sa20, ilt20, county, wbbl, wpl, hundred_women.
searchNoPart of the team name.
seasonNoSeason: a year (2024) or a split season (2024/25); a year also finds the split season that starts in it.
competitionNoCompetition key from list_competitions (ipl, bbl, psl, blast, hundred, county, test, odi, t20i, ...).

Output Schema

NameRequiredDescriptionDefault
countYes
teamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description's job is to add domain behavior — and it does: result ordering (most matches first), the -women id suffix convention with an example (india-women), the now_plays_as rename field and the fact that filtering on either id finds both records, plus a cost of 1 credit. These are non-obvious traits an agent could not get from the annotations or schema.

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?

The most decision-relevant information — what it returns and the id conventions — is front-loaded, and the trailing "Costs 1 credit" is a short, high-value constraint. No sentence is redundant or padded.

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 a rich output schema and full annotations, the description only needs to cover domain quirks, and it covers ordering, id naming, renames and cost. Minor gaps remain: it does not mention the default league (cricket, documented only in the schema) or whether results are capped/paginated, which matters for a listing tool that can return many teams.

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 80%, so the schema already documents league, season, competition and search. The description still adds meaning beyond it by naming the four filter axes together and by explaining the -women naming convention and the now_plays_as aliasing, which directly affect how search and gender filtering should be formed.

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?

"Use for team ids: international sides and franchises" names the resource (teams) and what the caller gets out of it (ids), which is more useful than restating the name. It implicitly separates itself from list_competitions by positioning itself as the id lookup for sides, though it never states that distinction 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?

"Use for team ids" gives a clear reason to call this tool, and "Filter by competition, season, gender or part of a name" tells the agent which narrowing dimensions are available. There is no explicit when-not-to-use guidance or named alternative, 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.

All YorkerAPI toolsInspect
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