Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_series

Discover current and upcoming cricket series grouped by month, with IDs, dates, and URLs; filter by category, live streaming, or name substring.

Instructions

Discover Cricbuzz current and future series. Returns current and future series grouped by month, with series IDs, dates, and canonical URLs. Filter by the live route-backed category, the Live Streaming flag, or a local case-insensitive series-name substring. Live Streaming may validly return an empty result set when Cricbuzz has no matching entries at the time of the request.

Input Schema

NameRequiredDescriptionDefault
qNoOptional local substring search over series names, up to 100 characters
categoryNoSeries category; defaults to all
live_streamNoRestrict to Cricbuzz's Live Streaming page filter

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 full burden and does well: it discloses the return shape (grouped by month, series IDs, dates, canonical URLs), that q is a local case-insensitive substring match, that category is a 'route-backed' Cricbuzz category, and that Live Streaming can legitimately return zero rows. It stops short of stating rate limits or pagination 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?

Four sentences, front-loaded with the purpose and return payload; every sentence contributes content. Minor redundancy in restating 'current and future series' twice in the first two sentences.

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?

No output schema exists, and the description compensates by enumerating the returned fields and grouping. For a three-optional-parameter discovery tool this is nearly sufficient; pagination or result-count limits are the only notable omission.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by clarifying that the name search is performed locally and case-insensitively and that category is the live route-backed category rather than an arbitrary grouping. That is genuine added semantic value over the enum list.

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?

States a specific verb and resource ('Discover Cricbuzz current and future series') and delimits scope to current/future, which implicitly separates it from archive-style siblings like cricbuzz_archives. It does not name a sibling explicitly, so an agent must still infer the boundary against cricbuzz_schedule and cricbuzz_matches.

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 ('Discover... series') and the three filter modes are described, but there is no explicit statement of when to prefer this over cricbuzz_archives or cricbuzz_schedule, nor any exclusion. The empty-result caveat for Live Streaming is a useful operational note rather than a routing rule.

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