Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_info

Retrieve a selected cricket auction edition’s guide with labelled date, venue, auctioneer, purse/roster rules, FAQs, and currency-rate blocks as source text.

Instructions

Get the Cricbuzz auction guide. Returns all labelled text and list blocks shown in the selected edition's Auction Guide. The guide's fields vary by competition and season; date, venue, auctioneer, purse/roster rules, FAQs and currency-rate blocks are preserved as source text.

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; defaults to 2026 when both tournament/year are omitted
tournamentNoTournament identifier from cricbuzz/auction/seasons: ipl, wpl, sa20, hunm, hunw; defaults to ipl when both tournament/year are omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden, and it does usefully disclose that the guide returns labelled text and list blocks as source text, with fields varying by competition and season. However, it does not explicitly confirm read-only behavior, describe output structure, or mention any operational constraints such as rate limits or authentication.

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?

The description is short, front-loaded, and structured as three purposeful sentences: the action, the return content, and the field variability. It does not waste space on repetition, though the third sentence is somewhat list-heavy.

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?

Given two optional parameters with full schema coverage and no output schema, the description provides adequate context about what is returned and why fields vary by edition. It would be stronger if it explicitly stated read-only behavior or clarified whether the guide includes historical vs current auction editions.

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?

The schema has 100% description coverage, including enumerated year/tournament values and defaults, so the description only needs to add meaning beyond that. It does connect the parameters to 'selected edition' and notes that fields vary by competition and season, but it does not add syntax or selection detail 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 verb and resource: it gets the Cricbuzz auction guide and returns all labelled text and list blocks from the selected edition's guide. The resource 'auction guide' is distinct from live auction, results, news, and video siblings, though the description does not explicitly name or differentiate against them.

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

Usage Guidelines2/5

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

The description explains what the tool returns but gives no explicit guidance on when to use it instead of related cricbuzz auction tools such as live updates, results, upcoming auctions, or seasons. Usage is only implicit from the resource name 'auction guide'.

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