Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_match_graphs

Retrieve numeric Cricbuzz match graphs—runs, run rate, runs per over, win probability, innings, and wicket-over values—from a canonical match URL, excluding commentary and media.

Instructions

Get numeric Cricbuzz match graphs. Returns the first-party Graphs page's runs, run-rate, runs-per-over, win-probability, innings, and wicket-over values. Commentary prose and media are omitted. Pass the canonical match URL returned by /cricbuzz/matches.

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.2/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 a fair job: it declares the data is numeric/first-party, and explicitly states that 'Commentary prose and media are omitted', preventing an agent from expecting narrative content. It does not address auth, rate limits, or whether partial data is returned for a not-yet-started match.

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 short sentences, front-loaded with the purpose, then the payload contents, then the omission caveat and input requirement. No filler or repetition.

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 and no annotations, the description must convey return content, which it does by enumerating the metric series. Remaining gaps are edge cases (behavior for live vs. completed matches, partial-series availability), which are minor for a single-param read tool.

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?

Only one parameter, and schema coverage is 100%, so the schema already defines match_url fully. The description restates the same provenance rule ('canonical match URL returned by /cricbuzz/matches') rather than adding new detail such as URL format or handling of non-canonical URLs, 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 ('Get') plus a specific resource ('Cricbuzz match graphs'), followed by an enumeration of exactly what numeric series come back (runs, run-rate, runs-per-over, win-probability, innings, wicket-over). This clearly separates it from siblings like cricbuzz_scorecard, cricbuzz_match_overs, or cricbuzz_match_facts without needing the schema.

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 prerequisite for invocation ('Pass the canonical match URL returned by /cricbuzz/matches'), which tells an agent where the input must come from. It also implicitly scopes usage by excluding prose/media. It stops short of explicitly naming competing tools (e.g. scorecard vs. graphs) or saying when not to use it.

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