Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_upcoming

Fetch one page of filtered Cricbuzz unauctioned players by tournament, year, and currency, then narrow results by country, role, cap, and base-price sort.

Instructions

Get filtered Cricbuzz unauctioned players. Returns one 1-based page of unauctioned players. Discover tournament/year/currency via auction/seasons and exact Country/Role/Cap/Sort values via auction/upcoming/options. Country IDs are comma-separated and can be selected together; sort values are Base Price: High to Low and Base Price: Low to High. The source returns up to 20 rows and no total or has-more flag.

Input Schema

NameRequiredDescriptionDefault
capNoExact Cap option value from auction/upcoming/options; values: Capped, Uncapped
pageNoOne-based page number; defaults to 1
roleNoExact Role option value from auction/upcoming/options; SA20 2027 labels: All, Batter, Bowler, All Rounder, WK Batter
sortNoSort label from auction/upcoming/options: Base Price: High to Low, Base Price: Low to High
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
country_idsNoComma-separated exact Country option values from auction/upcoming/options; SA20 2027 labels: Afghanistan, Australia, Bangladesh, Canada, England, Hong Kong China, India, Ireland, Italy, Jersey, Kenya, Namibia, Nepal, Netherlands, New Zealand, Pakistan, Scotland, Singapore, South Africa, Sri Lanka, Thailand, United Arab Emirates, United States of America, West Indies, Zimbabwe

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 well: it discloses 1-based paging, a 20-row cap, and critically that there is no total or has-more flag so the agent knows it cannot detect the last page. It does not mention auth or rate limits, but the paging/limit disclosure is the operationally important part.

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?

Front-loads the core purpose in the first sentence, then tacks on discovery guidance and the pagination caveat. Dense but each sentence adds operational value; only the sort-value enumeration mildly duplicates the schema.

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 an 8-param, no-output-schema, no-annotation read tool, the description covers the essentials an agent needs: valid value sources, paging behavior, result cap, and absence of pagination signals. Sufficient to call it correctly, though it could note what fields each player row contains if a caller needs to plan post-processing.

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 coverage is 100%, so the schema already documents all 8 params including enum-like values. The description adds a little extra meaning ('Country IDs are comma-separated and can be selected together'), but mostly restates what the schema already says. Baseline 3 is appropriate.

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 filtered Cricbuzz unauctioned players') and immediately clarifies it returns unauctioned players only. It doesn't explicitly contrast with siblings like cricbuzz_auction_results or cricbuzz_auction_player, but the resource is concrete enough to distinguish it.

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 tells the agent where to obtain valid tournament/year/currency values (auction/seasons) and Country/Role/Cap/Sort values (auction/upcoming/options), which is the key prerequisite for calling it with 100%-description'd but enum-less params. It stops short of stating when to prefer this over sibling auction tools.

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