Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_records

Retrieve a bounded table from a Cricinfo Statsguru record page by specifying a relative record path and match class.

Instructions

Get a Cricinfo record table. Returns a bounded table from a 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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the output is a *bounded* table (implying truncation) and that `record` is a relative Statsguru path, but says nothing about permissions, how `class` changes results, or pagination/size limits.

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?

Three front-loaded sentences with the core purpose first, then the return shape, then parameter notes. Slight redundancy in re-listing the full class enum already present in the schema, but no filler.

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 5-param (2 required) tool with a complete schema but no annotations or output schema, the description covers the required parameters and the return form adequately. The optional `id`, `type`, and `current` params are left purely to the schema, which is acceptable given 100% coverage.

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 description coverage is 100%, so the baseline is 3, but the description adds an illustrative path (`batting/most_runs_career.html`) and frames `class` as the 'match-class' selector, giving meaning beyond the raw enum that the schema only enumerates.

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 ('Get a Cricinfo record table') and clarifies the return is a bounded table from a records page, which an agent can tell apart from index-style siblings. It does not name the obvious sibling cricinfo_records_index that supplies the paths, so it falls short of 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 Guidelines3/5

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

Usage is only implied: the agent can infer it needs a valid Statsguru path from `record`'s example format, but there is no explicit when-to-use, prerequisites, or pointer to cricinfo_records_index as the source of valid paths.

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