Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_stats

Query Cricinfo Statsguru to retrieve bounded cricket statistics tables filtered by match class, statistic type, player, team, venue, or season.

Instructions

Query Cricinfo Statsguru. Returns a bounded 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

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. It hints at bounded output ('a bounded Statsguru table') but does not disclose return shape, pagination, column structure, rate limits, or auth requirements. For a 14-parameter query tool with no annotation coverage, this is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core statement well, but then spends most of its length enumerating enum values that are already fully specified in the schema. That enumeration does not earn its place and crowds out more useful information such as return format or when to prefer this over sibling tools.

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?

For a 14-parameter tool with no output schema and no annotations, the description is not complete enough. It leaves the return structure, default behaviors, and the mapping of numeric identifiers (player, team, ground, opposition) unexplained, all of which an agent would need to invoke it correctly.

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 description coverage is 100%, so the schema already documents every parameter. The description restates the allowed values for class, type, and view, but this duplicates the enums rather than adding semantic meaning (e.g., what class values 1 vs 20 represent, or how span_min/span_max interact). Baseline 3 applies.

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?

States a specific verb and resource: 'Query Cricinfo Statsguru' returning 'a bounded Statsguru table.' This is clear enough for an agent to identify it as the stats-query tool. However, it does not differentiate from sibling stats tools like cricinfo_records or cricinfo_rankings, so the agent must infer the distinction.

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

Usage Guidelines2/5

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

Provides no when-to-use guidance or alternatives. An agent cannot tell from the description whether to call this versus cricinfo_records, cricinfo_rankings, or cricinfo_records_index. The only constraints given are enum value lists, which are schema concerns, not usage guidance.

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