Crawlora MCP

cricbuzz_rankings

Read-only

Returns an ICC ranking table from Cricbuzz. Discover men or women, batting, bowling, all-rounder or teams, and the gender-specific formats: men Test/ODI/T20, women ODI/T20.

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": {
      "Gender": "<Gender>",
      "Type": "<Type>",
      "Format": "<Format>"
    },
    "name": "cricbuzz_rankings"
  }
}

Input Schema

Name	Required	Description
`Type`	Yes	Ranking table type; defaults to batting. Documented values: batting, bowling, all-rounder, teams.
`Format`	Yes	Ranking format; defaults to the page's selected format. The valid set depends on gender. Documented values: test, odi, t20.
`Gender`	Yes	Ranking gender; defaults to men. Documented values: men, women.

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 and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses that available formats are gender-dependent (women only ODI/T20, men Test/ODI/T20), which prevents invalid calls.

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?

Two compact sentences, front-loaded with the core action and followed by the option space. No wasted phrasing, though the format enumeration is slightly listy and could be tighter.

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?

An output schema exists, so return values need not be explained. The description covers all three parameters and the key gender/format dependency, leaving only minor gaps like ranking period or pagination details.

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 baseline is 3. The description adds meaning beyond the schema by spelling out the valid gender/format combinations, helping the agent understand the conditional constraint between Gender and Format parameters.

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 ('Returns') and resource ('ICC ranking table from Cricbuzz') and enumerates the dimensions available (gender, batting/bowling/all-rounder/teams, formats). It is clearly distinct from other Cricbuzz tools, though it does not explicitly differentiate itself from the sibling cricinfo_rankings.

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 value space is described but there is no explicit when-to-use/when-not guidance or naming of an alternative (e.g., cricinfo_rankings). Usage is only implied by listing the selectable dimensions.

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?