Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_stats

Retrieve cricket statistics from Cricinfo Statsguru by match class, statistic type, and view. Returns a normalized table of batting, bowling, fielding, or team data for analysis.

Instructions

Query Cricinfo Statsguru. Returns a bounded normalized Statsguru table. class must be one of 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 20, 21, 22, or 23; type must be one of batting, bowling, fielding, allround, fow, team, official, or aggregate; view may be innings, match, series, ground, host, opposition, year, or season.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoNumeric host-country identifier
teamNoNumeric Cricinfo team identifier
typeYesStatsguru statistic family
viewNoStatsguru table view
classYesStatsguru match-class. Allowed values: 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 20, 21, 22, 23
limitNoMaximum rows returned, from 1 to 100
groundNoNumeric ground identifier
playerNoNumeric Cricinfo player identifier
seasonNoSeason formatted as YYYY or YYYY/YY
orderbyNoStatsguru sort column
span_maxNoStatsguru ending date
span_minNoStatsguru starting date
oppositionNoNumeric opposition team identifier
orderby_descNoSort descending when true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / class / enum
      Added value: +[
+  1,
+  2,
+  3,
+  4,
+  5,
+  6,
+  8,
+  9,
+  10,
+  11,
+  12,
+  20,
+  21,
+  22,
+  23
+]
    • addedInput schema / properties / type / enum
      Added value: +[
+  "batting",
+  "bowling",
+  "fielding",
+  "allround",
+  "fow",
+  "team",
+  "official",
+  "aggregate"
+]
    • addedInput schema / properties / view / enum
      Added value: +[
+  "innings",
+  "match",
+  "series",
+  "ground",
+  "host",
+  "opposition",
+  "year",
+  "season"
+]
  2. Addedv1.16.2

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that a 'bounded normalized Statsguru table' is returned, which hints at pagination or limits but does not mention read-only semantics, error behavior, rate limits, or the structure of the returned data. This is insufficient for a query tool 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?

The description is a single efficient sentence that front-loads the tool's purpose and then lists valid values. While the value lists are long, they are necessary and not padded. It could be better structured with bullets, but it is not verbose.

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

Completeness2/5

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

Given the tool's complexity (14 parameters, no output schema, no annotations), the description is inadequate. It does not explain the meaning of key parameters like player, team, ground, or span_min/span_max beyond their schema descriptions, nor does it clarify how results are ordered or how pagination works. An agent cannot confidently construct a correct query without deeper context.

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 baseline is 3. The description repeats the allowed values for class, type, and view, which are already covered by schema enums, adding no new meaning. It does not explain how to combine parameters or interpret their semantic relationships beyond what the schema already provides.

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?

The description clearly states the verb 'Query' and the resource 'Cricinfo Statsguru', making the tool's purpose unambiguous. It differentiates from siblings like cricinfo_match or cricinfo_rankings by focusing on Statsguru tables, though it does not explicitly name alternatives.

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?

The description implies usage for querying historical cricket statistics via Statsguru but provides no explicit guidance on when to choose this tool over other cricinfo tools (e.g., cricinfo_scores, cricinfo_rankings). It only lists allowed enum values, which is more about parameter validation than usage context.

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