Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_team_stats_options

Discover a Cricbuzz team's batting and bowling stats topics, format IDs, year values, and opponent IDs, then use the returned values to query team statistics.

Instructions

Discover team statistics topics and filters. Returns the selected team's complete Batting and Bowling topic menus, supported format IDs, every year value and every opponent ID from Cricbuzz's team Stats page. Discover team_id and category from /cricbuzz/teams; use the exact dynamic values returned here with /cricbuzz/team/stats. The source page exposes no sort control.

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam ID returned by /cricbuzz/teams for the selected category
categoryYesTeam-directory category from /cricbuzz/teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description must carry the burden: it discloses that the tool returns complete topic menus and dynamic ID sets (a read-only discovery call), and notes a real page limitation ('no sort control'), which pre-empts a wrong assumption. It stops short of stating whether results are cached or how large the returned menus can be.

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?

Four tight sentences with the return contents front-loaded, then the workflow chain, then the sort limitation. Every sentence carries distinct information and none is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter discovery tool with no output schema, the description supplies enough: what the response contains (topic menus, format/year/opponent IDs), where the inputs come from, where the outputs go, and a page constraint. Nothing an agent needs to call it correctly is missing.

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 baseline is 3; the description adds value by stressing that the parameters must be the exact dynamic values from /cricbuzz/teams and that both flow into the follow-up call, which clarifies provenance beyond the schema's field descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Discover team statistics topics and filters') and enumerates exactly what is returned: Batting/Bowling topic menus, format IDs, year values and opponent IDs. An agent can distinguish this discovery tool from the sibling cricbuzz_team_stats (the stats endpoint) without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: get team_id/category from /cricbuzz/teams, then feed the exact dynamic values returned here into /cricbuzz/team/stats. This names the upstream source, the downstream consumer, and the chain requirement, leaving nothing to inference.

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