Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_options

Fetch filter dropdown values and sort choices for a selected Cricbuzz completed auction edition, with tournament and year inputs; returns options dynamically for building accurate queries.

Instructions

Discover Cricbuzz auction filters and sort values. Returns all filter dropdown values and sort choices embedded in the selected public completed-auction page. Use auction/seasons to discover current tournament and year values; when omitted, tournament and year default to ipl and 2026. Filter and sort values vary by edition and are returned dynamically.

Input Schema

NameRequiredDescriptionDefault
yearNoEdition from cricbuzz/auction/seasons: ipl 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026; wpl 2023, 2024, 2025, 2026, 2027; sa20 2027; hunm 2026; hunw 2026
tournamentNoTournament identifier from cricbuzz/auction/seasons; current values: ipl, wpl, sa20, hunm, hunw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/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 reasonably well: it discloses that the data is scraped from the selected public completed-auction page, that filter and sort values vary by edition, and that values are returned dynamically rather than being a fixed enum. It does not state read-only semantics or rate/refresh limits, which is the main residual gap.

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 what the tool returns before the dependency and default caveats. Slight redundancy between 'Discover Cricbuzz auction filters and sort values' and 'Returns all filter dropdown values and sort choices', but nothing is wasted overall.

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, read-only discovery tool with no output schema, the description covers what is returned, where it comes from, defaults, and variability across editions. An agent has enough to call it correctly; only the exact response envelope and read-only framing are left unstated.

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 both parameters are already documented with valid values. The description adds genuinely new meaning beyond the schema: the default fallbacks (ipl, 2026) when parameters are omitted, and the fact that the returned option set changes with the chosen edition.

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 auction filters and sort values' and elaborates that it returns filter dropdown values and sort choices from a completed-auction page. The scope word 'completed-auction' implicitly separates it from cricbuzz_auction_upcoming_options and cricbuzz_auction_teams_options, but those siblings are never named, so distinction is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear usage context: call cricbuzz_auction_seasons first to discover tournament and year values, and it documents what happens when they are omitted (defaults to ipl/2026). It stops short of explicitly saying this should precede a call to cricbuzz_auction_results or that it is unnecessary for live/upcoming auctions, so the workflow routing is only partly spelled out.

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