Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_team_stats

Fetch a selected cricket team's batting or bowling statistics table by category, team, stat, format, year, and opponent.

Instructions

Fetch one team statistics table. Returns the selected team's Batting or Bowling table. First call /cricbuzz/team/stats/options with the same category and team_id. stat values currently exposed by India are mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties, mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon and lowestSr; each team may expose a subset. format_id, year and opponent_id must be exact values from the options response. The source page exposes no sort control; an explicitly empty upstream table returns empty_state=no_results.

Input Schema

NameRequiredDescriptionDefault
statYesA value returned for the selected team by /cricbuzz/team/stats/options; current India values are mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties, mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr
yearYesYear value returned by /cricbuzz/team/stats/options, including all when offered
team_idYesTeam ID returned by /cricbuzz/teams for the selected category
categoryYesTeam-directory category from /cricbuzz/teams
format_idYesFormat ID returned by /cricbuzz/team/stats/options
opponent_idYesOpponent ID returned by /cricbuzz/team/stats/options, including all when offered

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the source page has no sort control and that an explicitly empty upstream table surfaces as empty_state=no_results, both non-obvious behaviors. What it does not cover is row limits/pagination or the columns of the returned table, which matters for a stats table with no output schema.

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?

Front-loaded with the purpose, then the prerequisite chain, then the caveats — a sensible ordering. The long inline enumeration of fifteen stat values duplicates the enum-like list already in the schema, so a sentence of it does not earn its place, but nothing else is wasted.

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 six-required-parameter read tool with no annotations and no output schema, the description covers the join path (options → teams → stats), the empty-result signal, and the absence of sorting. The remaining gap is the shape of the returned table (columns, row count), which an agent would otherwise have to discover empirically.

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 100%, so the parameters are already documented field-by-field, and much of the description's parameter text (stat values, 'returned by /cricbuzz/team/stats/options') restates the schema. The one genuine addition beyond the schema is the caveat that a team may expose only a subset of the enumerated stat values, which justifies the baseline 3.

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?

States a specific verb and resource ('Fetch one team statistics table') and pins the return to the selected team's Batting or Bowling table, so it is clearly not a match-level or series-level stats tool. It also names the prerequisite options endpoint, which disambiguates it from cricbuzz_team_stats_options in the sibling list.

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?

Gives an explicit call sequence ('First call /cricbuzz/team/stats/options with the same category and team_id') and states that format_id, year and opponent_id must be exact values from that response. It further warns that each team may expose only a subset of the listed stat values, which prevents guess-and-check invocation.

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

Deploy Server

Other Tools