Crawlora MCP

cricbuzz_records

Read-only

Returns Cricbuzz's full record-topic and filter-value discovery plus the selected records table. Use the returned options to choose a stat, format, year, team and opponent; each value is validated before the upstream JSON request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Stat": "<Stat>",
      "Format": "<Format>",
      "Year": "<Year>",
      "Team": "<Team>",
      "Opponent": "<Opponent>"
    },
    "name": "cricbuzz_records"
  }
}

Input Schema

Name	Required	Description
`Stat`	Yes	Record topic; defaults to mostRuns. Documented values: mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties, mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr.
`Team`	Yes	Team ID from the page's dynamically discovered Team options
`Year`	Yes	Year value from the page's dynamically discovered Year options
`Format`	Yes	Match format label; defaults to the current table format. Documented values: test, odi, t20.
`Opponent`	Yes	Opponent ID from the page's dynamically discovered Oppn options

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by explaining that the tool returns both discovery options and a selected records table, and that each chosen value is validated before the upstream JSON request.

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 two sentences and front-loads the main behavior before explaining parameter usage. It is efficient, though the first sentence is slightly dense with two discovery outputs plus the selected table.

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 five required parameters, annotations, and an output schema, the description supplies the key operational context: discovery-first selection and validation. It is complete enough for correct invocation, though sibling differentiation could be stronger.

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 coverage is 100%, so the schema already documents all five parameters. The description adds meaningful semantics by stating that the values for Stat, Format, Year, Team, and Opponent should come from the returned discovery options and are validated before the upstream request.

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 uses a specific verb, "Returns," and a specific Cricbuzz resource: record-topic discovery, filter-value discovery, and the selected records table. It is clear what the tool does, though it does not explicitly distinguish itself from sibling record tools such as cricinfo_records.

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?

It gives procedural guidance: use the returned options to choose a stat, format, year, team, and opponent. However, it does not state when to use this tool versus alternatives, nor does it identify conditions where another records 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.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?