Discover Cricbuzz auction leagues, editions, and currencies, returning each current menu value with its canonical season slug and accepted currencies from public season-details JSON.
Discover Cricbuzz auction leagues, editions and currencies. Returns every current League & Edition menu value, its canonical season slug and its accepted currencies from Cricbuzz's public season-details JSON.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.18Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden and does well: 'Discover' and 'Returns' imply a read-only lookup, and it discloses that results come from Cricbuzz's public season-details JSON and include every current League & Edition menu value with canonical slugs and currencies. Minor omissions like freshness or rate-limit behavior keep it from a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with the purpose and followed by the concrete return payload. Every element earns its place by clarifying scope and output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter discovery endpoint without an output schema, the description sufficiently explains what data comes back and its source. It could be slightly more complete by noting how the returned slugs should be used with dependent auction tools, but nothing essential for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description correctly adds no parameter detail because none are needed, and it stays consistent with the empty input schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource set: discovering Cricbuzz auction leagues, editions, and currencies, plus the concrete returned values (menu values, season slugs, accepted currencies). It is clear what the tool does, though it does not explicitly contrast itself with nearby options-oriented siblings such as cricbuzz_auction_options.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the word 'Discover' and the returned data. There is no explicit statement about when to call this tool versus alternatives, nor any guidance such as using it first to obtain slugs for other auction tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.