Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_match_facts

Fetch Cricbuzz match facts—title, toss, venue, officials, team squads, bench players, and support staff—from a canonical match URL to view complete match and squad details.

Instructions

Get Cricbuzz match information and squads. Returns the public Info-tab match title, toss, venue guide, umpires, third umpire, referee, both team squads, bench players, and support staff. Use the canonical match URL returned by /cricbuzz/matches. Squad member links are preserved where Cricbuzz publishes them.

Input Schema

NameRequiredDescriptionDefault
match_urlYesCanonical Cricbuzz live-cricket-scores URL returned by /cricbuzz/matches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it scopes output to the 'public Info-tab' (signalling metadata rather than live scores) and warns that squad member links are only kept 'where Cricbuzz publishes them,' which discloses partial/uneven data. It never explicitly states this is a read-only, side-effect-free call, which is the only notable gap.

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?

Three tight sentences, front-loaded with purpose then the return inventory, with the URL prerequisite stated in the middle. No filler and every clause contributes information.

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 single-parameter read tool with no output schema, the description must describe the payload — and it does so thoroughly, listing every returned section plus the link-preservation caveat. An agent has everything needed to call it and know what comes back.

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 coverage is 100% and the single parameter's description already explains that it is the canonical Cricbuzz live-cricket-scores URL from /cricbuzz/matches. The description's URL guidance duplicates the schema rather than adding format or edge-case detail, so baseline 3 applies.

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?

Specific verb and resource ('Get Cricbuzz match information and squads') followed by an explicit enumeration of the returned facts — title, toss, venue guide, umpires, referee, squads, bench, support staff. This clearly separates it from siblings like cricbuzz_scorecard or cricbuzz_match_overs, which cover scoring and ball-by-ball data.

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 states the entry condition ('Use the canonical match URL returned by /cricbuzz/matches') and implicitly frames this as the Info-tab metadata/squad lookup rather than live scoring. It does not explicitly name the alternative tools to use for scorecards or commentary, so the when-not guidance is inferred rather than stated.

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