Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_records

Fetch normalized cricket record tables from Cricinfo Statsguru using a record path and match class. Returns structured data for specific records.

Instructions

Get a Cricinfo record table. Returns a bounded normalized table from a public Cricinfo records page. record is a relative Statsguru record path such as batting/most_runs_career.html. class must be one of 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 20, 21, 22, or 23.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric record subject identifier
typeNoRecord subject type
classYesRecord match-class. Allowed values: 1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 20, 21, 22, 23
recordYesRelative Statsguru record path
currentNoRecord currentness selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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
+]
  2. Addedv1.16.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose useful behavioral traits: 'bounded normalized table' and 'public', which imply read-only access and a constrained result size. However, it does not mention error handling, rate limits, or what happens on invalid inputs, leaving gaps that annotations would normally fill.

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 description is two sentences with no filler. The first sentence states the core function, and the second clarifies the two required parameters with an example and enum list. Every element earns its place.

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?

Given the schema fully documents all parameters and the description explains the required ones well, an agent has enough context to invoke the tool. The mention of 'bounded normalized table' hints at the return format even without an output schema. Optional parameters are not explained beyond schema, but that is acceptable.

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 baseline is 3. The description adds a concrete example for `record` and restates the allowed `class` enum values, which is helpful. It does not add meaning for id, type, or current, but the schema already describes them adequately.

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 ('Get') and the resource ('Cricinfo record table'), and specifies the output as a 'bounded normalized table'. It distinguishes the tool's purpose by emphasizing the Statsguru record path and the class restriction. However, it does not explicitly name sibling tools like cricinfo_records_index, so it lacks full differentiation.

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?

No guidance is given on when to use this tool versus alternatives such as cricinfo_records_index or cricinfo_scores. The description implies it is for fetching specific records via a path, but does not state exclusions, prerequisites, or when another tool would be more appropriate.

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