Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_scorecard

Fetch a complete Cricbuzz match scorecard from a canonical match URL to get header, toss/result, venue, innings batting, bowling, totals, extras, powerplays, wickets, and partnerships; future matches return no_scorecard.

Instructions

Get a Cricbuzz match scorecard. Returns match header, toss/result, teams/venue, and every innings' batting, bowling, totals, extras, powerplays, wickets, and partnerships. Pass the canonical match URL returned by /cricbuzz/matches. Future matches can return an explicit no_scorecard state. Media assets are not returned.

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

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 full burden and does disclose non-obvious behavior: future fixtures can return an explicit no_scorecard state, and media assets are excluded from the response. It does not cover permissions/auth, pagination, or whether live in-progress matches return partial data, so it stops short of fully characterizing behavior.

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 payload description is front-loaded in sentence one, and the following sentences each add a distinct fact (returned sections, input provenance, edge state, exclusion). The input-sourcing sentence duplicates the schema's parameter description, which is the one small redundancy.

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?

With no output schema, the description compensates by enumerating the returned sections (header, toss/result, venue, innings batting/bowling/totals, powerplays, partnerships), plus an error state and an exclusion. Minor gaps remain on response structure and whether live matches behave differently, but everything needed to call it correctly 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 coverage is 100% and the single parameter already documents itself as "Canonical Cricbuzz live-cricket-scores URL returned by /cricbuzz/matches", so the description's sentence about the URL largely restates the schema. The added nuance is only the emphasis on "canonical", matching the baseline 3 for a schema-covered single parameter.

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?

It states a specific verb and resource ("Get a Cricbuzz match scorecard") and then enumerates the returned sections, which effectively separates it from sibling tools that only expose one slice of a match (cricbuzz_match_overs, cricbuzz_match_graphs, cricbuzz_match_facts). It never names those siblings explicitly, so the differentiation is inferred from content rather than stated.

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?

"Pass the canonical match URL returned by /cricbuzz/matches" gives a concrete prerequisite and the upstream tool that produces the input, which is exactly the guidance an agent needs before calling. There is no explicit when-not clause or alternative routing (e.g. versus cricbuzz_match_facts), which keeps it short of a 5.

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