Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_player

Retrieve a Cricbuzz auction player's profile and every auction-earnings row by player ID, tournament, year, and currency.

Instructions

Get a Cricbuzz auction player profile and earnings. Returns one player's current edition profile and every auction-earnings row in the public payload. Discover player_id through auction/player-search, auction/upcoming, auction/results or auction/team; discover currency through auction/seasons.

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
player_idYesPositive Cricbuzz player ID from an auction player result or team roster
tournamentYesTournament identifier from cricbuzz/auction/seasons: ipl, wpl, sa20, hunm, hunw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose what comes back ('every auction-earnings row in the public payload'), which implies a read-only, publicly accessible lookup, but it says nothing about pagination, rate limits, or failure behavior on a bad player_id/currency combination.

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 sentences, front-loaded with the tool's purpose, then the return payload, then input discovery. No filler and no repetition of schema content beyond what is needed to orient the agent.

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 annotations and no output schema, the description is the main source of context, and it covers purpose, inputs and return scope adequately for a four-required-parameter lookup. Remaining gaps (error handling, whether earnings span editions) are minor but nonzero for a tool with no structured safety hints.

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%, so the baseline is 3; the description goes further by naming the concrete tool endpoints to use when obtaining player_id and currency, which the schema descriptions do not. That discovery guidance is genuine added value beyond the field-level docs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a Cricbuzz auction player profile and earnings') and then pins down the exact return scope: one player's current-edition profile plus every auction-earnings row. This clearly separates it from discovery siblings like cricbuzz_auction_player_search, which it names as an input source rather than a competitor.

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?

Explicitly routes the agent to the right prerequisites, naming auction/player-search, auction/upcoming, auction/results and auction/team as sources of player_id, and auction/seasons for currency. It does not state any explicit 'do not use this for X' exclusion, but the prerequisite routing is clear enough that an agent knows when this tool is the right call.

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