Crawlora MCP

cricbuzz_matches

Read-only

Returns live, recent or upcoming Cricbuzz matches, with category filters for all, international, league, domestic and women. Includes canonical match URLs for scorecard, facts, graphs and over-by-over tools.

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": {
      "Status": "<Status>",
      "Category": "<Category>"
    },
    "name": "cricbuzz_matches"
  }
}

Input Schema

Name	Required	Description	Default
`Status`	Yes	Match-list status; defaults to live. Documented values: live, recent, upcoming.
`Category`	Yes	Match category; defaults to all. Documented values: all, 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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds useful context that results include canonical match URLs for scorecard, facts, graphs, and over-by-over tools, but it does not describe live-update behavior, freshness, pagination, or other operational traits.

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 tight sentences, with the primary purpose and status/category scope front-loaded. The second sentence adds relevant output context about canonical match URLs, so every sentence 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?

For a two-parameter list tool with a full output schema, the description is largely complete: it names the statuses, categories, and the useful canonical URL outputs. The main remaining gap is sibling routing—it does not explicitly say when to choose this over cricbuzz_schedule or cricinfo_live_matches.

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%, and the schema already documents defaults and allowed values for Status and Category. The description restates the same status and category values without adding syntax or selection guidance beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource: it returns Cricbuzz matches, scoped by live/recent/upcoming status and category. It also distinguishes the tool from detail-oriented siblings by noting that it includes canonical URLs for scorecard, facts, graphs, and over-by-over tools. An explicit contrast with schedule or live-score siblings is absent, keeping it from a 5.

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 status and category filters imply the tool is for browsing match lists by status and competition type, but the description never states when to use this instead of siblings such as cricbuzz_schedule, cricbuzz_scorecard, or cricinfo_live_matches. Usage is therefore implied rather than explicitly guided.

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?