Skip to main content
Glama

mcp-cricket

by io.github.asaraog
OverviewDiscussionsAdmin

cricket_minor_league_info

Read-only

Player records and league history for Minor League Cricket (the US domestic T20 league), from data this server holds: CricClubs scorecards for 2026 and results with grounds for 2023-2026, CricClubs' 2025 and 2026 batting tables, Wikipedia's 2021-2024 squads and leader tables (CC BY-SA 4.0) and a research record that sources every fact. Every argument is optional and they combine: player for a season-by-season card (add team when two players share a name); team for where they are based and play, their finals and a season's captain, wicketkeeper, players and results; team with opponent, date or both for one fixture's ground, result and 2026 top performers; ground; leaders with season and team; season alone for its champion, final and awards; topic for league facts. With no arguments it lists what it can answer. Each answer gives exact figures, its source and how current it is, and says what the data lacks. Names are matched whole: a surname several players share gets a question back, and a name the data lacks is said to be missing, never answered with another player's figures. Live scores and win chances are cricket_minor_league's.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoa day, YYYY-MM-DD, e.g. '2026-09-26': with team (and opponent) for that day's game, or alone for every game that day
teamNoa team's name, e.g. 'Chicago Kingsmen', 'All Stars' or 'Kingsmen'; 'Atlanta Fire v Atlanta Lightning' is read as a fixture. With player, it picks between players who share a name
topicNoa league-level fact: overview, format (season and playoffs), champions (every final), draft (roster rules), watch (tickets and streaming), history (founding and renamed teams), mlc (the pathway to Major League Cricket), teams (conferences and divisions)
groundNoa ground's name, e.g. 'Church Street Park', 'Grand Prairie' or 'NY Ovals'
playerNoa player's full name, e.g. 'Andries Gous'. A surname alone works when only one player has it
seasonNoa season, 2020-2026. Alone, that season's champion, final and awards; with other arguments, it narrows them. Default 2026 where a season is needed
leadersNoa season's leaders: runs or wickets for 2021-2026, the rest for 2026. Narrow with season and team
opponentNothe other team, for a fixture with team

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly, non-destructive, openWorld), and the description adds substantial context beyond them: exact provenance of each dataset, licensing (CC BY-SA 4.0), freshness ('how current it is'), explicit statement of what data lacks, and whole-name matching that returns a question rather than another player's figures. This is unusually rich failure-mode disclosure.

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?

Purpose and sourcing are front-loaded, then a compact semicolon-delimited tour of argument combinations. Every sentence carries information, but the single dense paragraph is longer than ideal and could be split for scannability.

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 an 8-parameter, all-optional tool with no output schema, the description covers the combination logic, defaults, provenance, currency, and answer format ('exact figures, its source and how current it is'). 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; however the description adds cross-parameter combination semantics (team+opponent+date for a fixture, player+team for disambiguation, season narrowing other arguments, default 2026) that the flat schema cannot express. It stops short of adding per-parameter syntax beyond what the schema already gives.

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?

Opens with a specific verb+resource ('Player records and league history for Minor League Cricket') and immediately scopes the data (CricClubs scorecards 2026, results/grounds 2023-2026, Wikipedia squads 2021-2024). It also names the sibling it is not, cricket_minor_league, for live scores, so the agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Enumerates concrete usage patterns for every argument combination (player, team+opponent, ground, leaders+season, season alone, topic, no arguments) and states the fallback behavior when no arguments are given. It explicitly routes live-score queries to cricket_minor_league.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-cricket 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