Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_team_schedule

Retrieve a cricket team's match schedule from Cricinfo using its canonical team URL. Returns fixtures, results, scores, and scorecard links.

Instructions

Get a Cricinfo team match schedule. Returns a cricket team's recent fixtures and results from its Cricinfo team page, given as the required url, which must be a canonical https://www.cricinfo.com/team/... address. The response has the team's id, name and slug, and matches with series, format, state, status text, team scores and scorecard URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Cricinfo team URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It conveys that this is a read-style fetch ('Get... Returns'), the required canonical URL constraint, and a detailed list of response fields, which is useful. It omits auth/rate-limit/pagination behavior, so it falls short of a rich behavioral profile.

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?

Three sentences, purpose front-loaded, then input constraint, then return shape. Efficient with no filler, though the response-field enumeration is slightly dense for a description that could lean on structure.

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?

Since no output schema exists, the description must describe the return; it does so (id, name, slug, matches with series/format/state/status/scores/scorecard URL). For a single-parameter tool this is complete, with only minor gaps around pagination or coverage.

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. The description adds real value beyond the schema's terse 'Canonical Cricinfo team URL' by specifying the exact required format ('https://www.cricinfo.com/team/...'), which meaningfully constrains how to supply the 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?

States a specific verb+resource (get team match schedule) and elaborates that it returns fixtures and results from a Cricinfo team page. It is clearly distinct from cricinfo_team (team detail) in intent, though it doesn't explicitly name that sibling to disambiguate.

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 — the agent can infer this is for retrieving a team's recent fixtures/results. However, there is no explicit when-to-use, when-not-to-use, or comparison against siblings like cricinfo_team or cricinfo_venue_matches, and no prerequisites 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