Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_matches

Lists Cricbuzz live, recent, or upcoming matches by category, returning match cards with teams, scores, venue, time, status, and canonical live-score URLs.

Instructions

List Cricbuzz live, recent, or upcoming matches. Returns Cricbuzz match cards grouped by source category and series, including teams, scores when available, venue, time, status, and the canonical live-score URL for detail endpoints. The homepage-only Live Now and Today controls are not included because their effects were not verified. Category filtering is local over the route-backed match groups.

Input Schema

NameRequiredDescriptionDefault
statusNoMatch-list status; defaults to live
categoryNoMatch category; defaults to all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/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 burden and does well by disclosing return structure: match cards grouped by source category and series, with teams, scores, venue, time, status, and canonical URL. It also transparently notes excluded homepage controls and that category filtering is local over route-backed groups.

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 with the core listing purpose and remains appropriately sized. Each sentence contributes relevant return-shape or filtering context, though the caveat about homepage-only controls could be stated slightly more compactly.

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?

There is no output schema, so the description must explain return values, which it does in useful detail. It covers the main result shape and filtering behavior, but it does not mention pagination, limits, or read-only safety explicitly, leaving minor gaps for an agent.

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?

The schema already documents both parameters at 100% coverage, establishing a baseline of 3. The description adds useful semantics by clarifying that category filtering is local over route-backed match groups, which affects how the category parameter should be interpreted.

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: list Cricbuzz live, recent, or upcoming matches. It clearly defines the listing scope and return content, though it does not explicitly name sibling tools like cricbuzz_scorecard or cricbuzz_schedule as alternatives for deeper match data.

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 description implies usage through status options and mentions that the returned URL is for detail endpoints, but it does not explicitly say when to use this tool versus sibling match or scorecard tools. The caveat about homepage-only controls is useful but does not provide alternative routing 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