Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

cricbuzz_series_stats

Read-only

Returns the available Cricbuzz series-stat topics and formats plus the selected series table. Pass a canonical series_url from cricbuzz_series and optionally a stat topic and format ID from the response's categories/formats. Team/Season values are discovery-only when their complete options are unavailable.

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": {
      "SeriesURL": "<SeriesURL>",
      "Stat": "<Stat>",
      "Format": "<Format>"
    },
    "name": "cricbuzz_series_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
StatYesStat topic; defaults to the currently selected topic. Documented values: mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties, mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr.
FormatYesFormat ID from the response's dynamic formats list; defaults to the current page selection
SeriesURLYesCanonical series URL returned by /cricbuzz/series

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior beyond annotations: the response supplies available topics/formats, and Team/Season values are discovery-only when complete options are unavailable. It does not add auth or rate-limit details, but with annotations present that is acceptable.

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 front-loaded and compact at three sentences, with no obvious filler. The final sentence about Team/Season is slightly opaque, but it is still relevant context rather than waste.

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 an output schema, 100% parameter coverage, and read-only/open-world annotations, the description supplies the important discovery workflow and parameter provenance. The main remaining gap is the required-vs-optional ambiguity around Stat and Format, plus the slightly vague mention of the 'selected series table'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented in structured form. The description adds provenance for SeriesURL and dynamic sources for Stat/Format, but it calls Stat and Format 'optional' while the input schema marks all three as required, creating a meaningful contradiction for invocation behavior.

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 gives a specific action and resource: returning Cricbuzz series-stat topics, formats, and the selected series table. It also points to cricbuzz_series as the source of the canonical URL, which helps distinguish its role from the series lookup tool. However, 'selected series table' is somewhat vague and it does not explicitly distinguish itself from related stat/records tools.

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?

It gives clear setup context: obtain SeriesURL from cricbuzz_series and choose Stat/Format from the response's categories/formats. That is useful usage guidance, though it does not state when to prefer this tool over sibling stat or records tools. The 'discovery-only' note adds context but is not a full alternative-selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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