Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_series_stats

Retrieve Cricbuzz series batting and bowling statistics by selecting a stat topic and format, returning the filtered stats table and available option values for a series.

Instructions

Discover Cricbuzz series statistics. Returns all Batting/Bowling statistic topics and format values for a series, its selected filter state, and selected stats table. stat and format are validated against the page's dynamic option lists and fetched via the first-party series-stats route. Team/Season filter values are not accepted because their complete option sets have not been confirmed.

Input Schema

NameRequiredDescriptionDefault
statNoStat topic; defaults to the currently selected topic
formatNoFormat ID from the response's dynamic formats list; defaults to the current page selection
series_urlYesCanonical series URL returned by /cricbuzz/series

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does well: it explains that stat and format are validated against dynamic option lists, that data is fetched via the first-party series-stats route, and that Team/Season filters are intentionally rejected. It does not cover auth, rate limits, or full output shape, but adds meaningful context beyond a bare label.

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 compact and front-loaded: purpose first, return contents second, validation behavior third, and the Team/Season exclusion last. Every sentence carries actionable information without repetition.

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 three parameters and no output schema, the description is nearly complete: it explains what is returned, how stat/format are validated, and which filters are unsupported. A slightly more explicit link to the series_url source or sibling alternative would make it fully self-contained.

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 parameters with defaults. The description adds useful meaning by noting validation against dynamic option lists and explicitly excluding Team/Season filter values, which helps an agent avoid invalid inputs.

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 the specific resource (Cricbuzz series statistics) and what it returns: batting/bowling statistic topics, format values, selected filter state, and selected stats table. It is clear but does not explicitly differentiate itself from siblings such as cricbuzz_series or cricbuzz_team_stats.

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 implies usage by describing the series-stats context and by noting that Team/Season filter values are not accepted. However, it does not explicitly say when to use this tool versus sibling tools or name an alternative for cases where series-level stats are insufficient.

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

Deploy Server

Other Tools