Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_schedule

List Cricbuzz matches by day, grouped by date and series, and filter by category or keyword to find relevant games in the current schedule window.

Instructions

List Cricbuzz matches by day. Returns every match in the current date window shown by Cricbuzz's Matches By Day page, grouped by date and series. Category and q filters run locally over that complete page payload. The date window is dynamic and can change with the upstream page.

Input Schema

NameRequiredDescriptionDefault
qNoOptional case-insensitive substring search over series, match descriptions, and team names, up to 100 characters
categoryNoSchedule 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 full burden and does disclose non-obvious behavior: results are grouped by date and series, the date window is dynamic and can shift with the upstream page, and category/q filtering happens locally over the complete payload rather than narrowing the fetch. It omits return shape, pagination and rate limits, keeping it short of a 5.

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 short sentences, front-loaded with the core action and ending with the caveat about the shifting window. The second sentence partially restates the first ('every match in the current date window'), a minor 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?

For a two-optional-parameter, no-output-schema listing tool this is close to sufficient: aggregation shape (by date and series) and the volatility of the window are both stated. What is missing is return volume or pagination expectations, which matters for a full-page payload.

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 baseline is 3, but the description adds real meaning by explaining that category and q run locally over the complete page payload — telling the agent the filters narrow the returned set, not the upstream scope. It adds no syntax detail beyond that.

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 ('List Cricbuzz matches by day') and pins the scope to the 'Matches By Day page' with a dynamic date window. It is clear what data comes back, though it never names sibling cricbuzz_matches or cricbuzz_archives to explain how this differs from them.

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?

'List Cricbuzz matches by day' plus the note about a dynamic window implies when the tool applies, but there is no explicit when-to-use / when-not or named alternative. An agent must infer that historical or broader schedules belong to cricbuzz_archives rather than being told so.

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