Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_live

Fetch the current Cricbuzz auction Live-tab data, including status, state, and featured players, without relying on a bid-event feed.

Instructions

Get the current Cricbuzz auction Live-tab payload. Returns current_status, state and featured/editor-pick players from the edition's Live tab. This is not a bid-event feed; a completed edition may return featured players without live bidding.

Input Schema

NameRequiredDescriptionDefault
yearYesEdition 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
currencyYesCurrency accepted by the selected edition: INR, USD, EUR, GBP, AUD, CAD, NZD, AED, ZAR, PKR, LKR, BDT, NPR
tournamentYesTournament identifier from cricbuzz/auction/seasons: ipl, wpl, sa20, hunm, hunw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden: it enumerates the returned fields (current_status, state, featured/editor-pick players) and warns that a completed edition may return featured players with no live bidding — a genuinely useful non-obvious behavior. It does not state that it is a read-only call or mention pagination/rate limits, so it stops short of full disclosure.

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?

Three tight sentences, front-loaded with what is returned, followed by the one caveat that matters. No restatement of the title and no 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?

With no output schema and no annotations, the description is the only place return shape and safety are conveyed, and it does describe the payload fields and the null-live-data edge case. Missing only read-only/no-auth confirmation and any hint about freshness or caching.

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% and all three parameters (tournament, year, currency) are fully documented there, including valid edition lists. The description only gestures at 'the edition's Live tab' without adding format or constraint detail beyond the schema, so the baseline 3 applies.

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 the current Cricbuzz auction Live-tab payload') and scopes it to current_status, state and featured players. It partially distinguishes itself from a bid-event feed, but never names the sibling it displaces (cricbuzz_auction_live_blog or cricbuzz_auction_results), so the sibling contrast is implied rather than explicit.

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?

The 'not a bid-event feed' caveat and the completed-edition note imply when this payload is and isn't appropriate, which is real usage context. However, no alternative tool is named for the bid-event or results use case, so the agent must infer the routing.

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