Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_auction_player_search

Search Cricbuzz auction players by tournament, year, and 3–100 character name query; returns matching player entries or an empty list when no players match.

Instructions

Search Cricbuzz auction players. Searches the current edition's public player index. q must contain 3-100 ASCII English letters or spaces, matching the source UI. A valid query with no matching players returns an empty items list.

Input Schema

NameRequiredDescriptionDefault
qYes3-100 ASCII English letters or spaces
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
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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that only the current edition is searched (not historical editions) and that a valid no-match query returns an empty items list, which prevents false-negative interpretation. It omits matching semantics (substring vs prefix), result caps/pagination, and any rate or access constraints.

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?

Four short sentences, front-loaded with the verb+resource, followed by scope, constraint, and edge-case behavior in a logical order. "matching the source UI" is slightly filler but earns its place as justification for the odd character restriction.

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 a 3-required-parameter search with no output schema, the description covers purpose, input constraint, scope limitation, and the empty-result case — enough to call it correctly. What result fields are returned is left unstated, but the "items list" mention gives a rough shape.

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%, so the schema already documents q's 3-100 ASCII letter/space rule and enumerates valid tournament/year values. The description restates the q constraint and adds the "current edition" framing for year, but adds no syntax or format detail beyond the schema. 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 ("Search Cricbuzz auction players") and adds scope ("current edition's public player index"), which separates it from the single-player sibling cricbuzz_auction_player. It never names that sibling explicitly, so differentiation is inferred rather than stated.

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?

Usage context is implied by "current edition's public player index" — an agent can infer this is for finding players within an already-chosen tournament/year. However, there is no explicit guidance on when to prefer this over cricbuzz_auction_player or cricbuzz_auction_teams, and no stated prerequisite that tournament/year values come from cricbuzz_auction_seasons.

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