Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_teams_options

Retrieve Cricbuzz auction team IDs, names, and available sort options for a tournament or year so you can query team details and sorted team lists correctly.

Instructions

Discover Cricbuzz auction teams and sort values. Returns all current team IDs and names plus the seven Teams-tab sorts: Alphabetical, Spent: High to Low, Spent: Low to High, Remaining: High to Low, Remaining: Low to High, Players: High to Low, Players: Low to High. Use the returned team_id values with auction/team and the sort labels with auction/teams.

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

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 full burden and does disclose the exact shape of the return (all current team IDs and names plus seven named sort labels), which implies a safe read-only enumeration. It omits whether the set is scoped by the year/tournament params or whether it can fail for unknown editions.

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-loaded with the purpose, then the returned values, then the consumption guidance — good ordering with no filler. Enumerating all seven sort labels is somewhat verbose since they are returned anyway, but it usefully tells the agent the exact label strings in advance.

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?

There is no output schema, so the description must explain return values — and it does, in detail. It is close to complete for a two-optional-param lookup tool; only the interaction between year/tournament and the team set is left implicit.

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% and both parameters already carry rich descriptions (valid editions, tournament ids, defaulting to 2026/ipl), so the baseline of 3 applies. The description adds nothing about how year/tournament affect the returned team set.

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?

Specific verb and resource ('Discover Cricbuzz auction teams and sort values') plus an explicit statement of the payload (team IDs, names, seven Teams-tab sort labels). It also names the downstream tools (auction/team, auction/teams), which separates it from the sibling listing tools, though it never says outright how it differs from cricbuzz_auction_teams.

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 concrete routing: 'Use the returned team_id values with auction/team and the sort labels with auction/teams' — a clear call-this-first pattern. No explicit when-not-to-use or prerequisite (e.g., must seasons be resolved first) is stated.

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