Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_rankings

Fetch ICC cricket rankings from Cricbuzz for men or women in batting, bowling, all-rounder, and teams, with Test, ODI, or T20 formats and explicit empty-table results.

Instructions

Get an ICC ranking table from Cricbuzz. Returns Men or Women rankings for Batting, Bowling, All rounder, or Teams. The format list is discovered from the selected category page; Men currently expose Test, ODI, and T20, while Women expose ODI and T20. Ranking rows are parsed from the page's embedded data, and empty ranking tables are reported explicitly.

Input Schema

NameRequiredDescriptionDefault
typeNoRanking table type; defaults to batting
formatNoRanking format; defaults to the page's selected format. The valid set depends on gender.
genderNoRanking gender; defaults to men

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does more than the minimum: it discloses that rows are parsed from embedded page data and that empty tables are reported explicitly, which tells an agent how failures/successes look. It omits any permission/auth or rate-limit notes, but this is a read tool where that matters less.

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, front-loaded with the core action and resource, then dimensions, then format-availability nuance, then return/edge-case behavior. Nothing is redundant and every sentence adds usable information.

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 3-param, no-output-schema, no-annotation tool, the description covers what is returned, the valid dimension combinations, and the empty-table edge case. It could say more about result shape or pagination, but it is largely self-sufficient for correct invocation.

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 already 100% with enums on all three params, so baseline is 3; the description adds genuine value by spelling out the gender-dependent format availability ('Men currently expose Test, ODI, and T20, while Women expose ODI and T20') and that format defaults to the page's selected format, which the schema only gestures at.

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: 'Get an ICC ranking table from Cricbuzz,' then enumerates what dimensions exist (Men/Women, Batting/Bowling/All rounder/Teams). The purpose is unambiguous, though it does not name a sibling (e.g., cricinfo_rankings) to differentiate itself in a very crowded rankings/stat tool set.

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 by the parameter description rather than stated: it tells you Men expose Test/ODI/T20 and Women ODI/T20, which indirectly guides selection, but there is no explicit when-to-use versus when-to-use-an-alternative guidance or any exclusions.

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