Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

cricbuzz_auction_player_search

Read-only

Searches the selected auction edition's player index. q accepts 3-100 ASCII English letters or spaces; valid no-match queries return an empty items list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tournament": "<tournament>",
      "year": "<year>",
      "q": "<q>"
    },
    "name": "cricbuzz_auction_player_search"
  }
}

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful behavioral detail by specifying q's character limits and stating that valid no-match queries return an empty items list, which helps an agent interpret results correctly.

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?

Two sentences, both earning their place: the first front-loads the purpose, and the second adds non-obvious query and no-match behavior. There is no redundant restatement of the tool name or annotations.

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?

All three parameters have full schema descriptions, an output schema exists, and annotations cover safety. The description is nearly complete for this low-complexity search tool, though a brief pointer to use cricbuzz_auction_player for player details would fully close the usage gap.

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%, and the schema already documents q, tournament, and year thoroughly. The description restates q's constraints and adds no-match behavior, but does not add meaning beyond the schema for the other parameters. 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?

The description states a specific verb and resource: 'Searches the selected auction edition's player index.' This is clear enough to distinguish a search-index operation from a player-detail tool, but it does not explicitly name or contrast with the sibling cricbuzz_auction_player.

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?

The phrase 'selected auction edition' implies that tournament and year must already be chosen, but the description never states when to use this tool versus cricbuzz_auction_player or other auction tools. Usage is only implied, not explicitly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources