Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_archives

Discover archive years and series on Cricbuzz, then fetch a selected year’s series grouped by category or filtered by keyword search.

Instructions

Discover Cricbuzz archive years and series. Returns all year links advertised by the Cricket Archives page and the complete series list for the selected year, grouped by the four visible archive categories. Supply year from the returned years array to fetch that year's page. category and q filter the full parsed series list locally.

Input Schema

NameRequiredDescriptionDefault
qNoOptional local case-insensitive substring search over selected-year series, up to 100 characters
yearNoArchive year from the years array in the response
categoryNoArchive series category; omit for all categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It discloses the return shape (year links, series grouped into four categories) and that category/q filtering is local, but it omits read-only status, auth needs, rate limits, and what happens when year is omitted.

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?

Four compact sentences with the purpose and workflow front-loaded. Every sentence adds concrete information without repetition or filler.

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 three-parameter, non-destructive discovery tool with full schema coverage and no output schema, the description is largely complete: it explains the resource, the year workflow, and local filtering. It could be stronger by clarifying default behavior when year is absent.

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 description coverage is 100%, so the parameters are already well documented. The description reinforces the intended flow ('supply year from the returned years array') but adds no new syntax or format details beyond the schema.

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?

The description states a specific resource (Cricbuzz archive years and series) and what is returned. The word 'archive' distinguishes it from current-series siblings like cricbuzz_series, though no sibling is explicitly named.

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?

It implies a two-step workflow: first discover years, then supply a year from the returned array. It also notes that category and q filter locally, but it never says when to use this tool versus alternatives or 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