Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_records

Discover Cricbuzz record topics and valid filter values, then fetch the selected record table. Validates filters against current page options before returning data.

Instructions

Discover Cricbuzz record topics and filter values. Returns all record-topic/filter values and the selected Cricbuzz record table. The first-party request path was cold-replayed; supplied filters are validated against the page's current discovery values before fetching data.

Input Schema

NameRequiredDescriptionDefault
statNoRecord topic; defaults to mostRuns
teamNoTeam ID from the page's dynamically discovered Team options
yearNoYear value from the page's dynamically discovered Year options
formatNoMatch format label; defaults to the current table format
opponentNoOpponent ID from the page's dynamically discovered Oppn options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses that the tool returns all record-topic/filter values plus the selected table and that supplied filters are validated against current discovery values before fetching, but it does not clarify read-only safety, error behavior, or whether invalid filters fail or are ignored.

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 short and front-loads the main purpose and return behavior. The phrase 'first-party request path was cold-replayed' is somewhat internal jargon that does not clearly earn its place, but overall the structure is efficient.

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 five-parameter optional-filter tool with no output schema and no annotations, the description covers the key behavior: it discovers filter values and returns both those values and the selected record table. It does not explain edge cases or sibling relationships, but the core information needed to call it is present.

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%, so the schema already documents all five parameters and their enums/defaults. The description reinforces that filter values must come from dynamically discovered options, but it adds no parameter-level meaning beyond what the schema provides.

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: discovering Cricbuzz record topics/filter values and returning the selected Cricbuzz record table. It is clear enough for an agent to know this is a records lookup tool, but it does not explicitly differentiate itself from nearby siblings such as cricinfo_records or cricbuzz_rankings.

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?

Usage is implied by 'Discover Cricbuzz record topics and filter values' and the note about validating supplied filters before fetching data, suggesting it should be used for records-table queries with discovery-backed filters. However, the description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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