Crawlora MCP

cricbuzz_archives

Read-only

Returns every year currently offered by Cricbuzz's Cricket Archives menu and the series for the selected year, grouped by international, league, domestic and women. Supply year only from the returned years list; category selects one of those groups and q filters series names locally.

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": {
      "Query": "<Query>",
      "Year": "<Year>",
      "Category": "<Category>"
    },
    "name": "cricbuzz_archives"
  }
}

Input Schema

Name	Required	Description
`Year`	Yes	Archive year from the years array in the response
`Query`	Yes	Optional local case-insensitive substring search over selected-year series, up to 100 characters
`Category`	Yes	Archive series category; omit for all categories. Documented values: international, league, domestic, 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

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only and open-world. The description adds genuinely new behavior: the call has two output modes (years catalog plus series for a chosen year), and q is applied locally rather than server-side, which affects result expectations. It doesn't mention result limits or pagination, keeping it at 4.

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?

Two sentences, no filler, and the primary behavior (returns years + series) is front-loaded before the parameter guidance. Every clause carries information an agent needs.

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?

With an output schema present, return shape needn't be explained, and the description covers both modes plus all three parameters. A minor gap is the tension between the schema marking Category as required and the description implying it simply 'selects one of those groups' with no all-categories path, which the agent can only resolve from the schema text.

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 earns above baseline by clarifying that Year is constrained to the values the response itself returns and that Query ('q') is a local substring filter rather than a remote search, meaning the schema's documented values are not exhaustive for Category.

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?

Specific verb+resource: returns the archive years list and the series for a selected year, grouped by four named categories. An agent can tell this is the archives browse endpoint rather than a live series/schedule tool. It does not explicitly name a sibling to contrast with, so it falls short of 5.

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

Usage Guidelines4/5

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

Gives a hard prerequisite ('supply year only from the returned years list'), which is real procedural guidance an agent couldn't infer. It explains category and q behavior but never states when to prefer this over cricbuzz_series or cricbuzz_schedule, so no exclusions or alternatives are offered.

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?