Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

cricbuzz_teams

Retrieve Cricbuzz team directories by category, including team IDs, short names, countries, images, and profile URLs. Optionally filter team names with a case-insensitive substring search.

Instructions

Discover Cricbuzz teams. Returns the complete team directory for one Cricbuzz category, with group labels, team IDs, short names, country labels, image IDs, and canonical team profile URLs. The optional q value performs a case-insensitive substring match on team names within the returned category.

Input Schema

NameRequiredDescriptionDefault
qNoOptional local substring search over team names, up to 100 characters
categoryNoTeam directory category; defaults to international

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and does well by stating that it returns the complete directory and that q performs a case-insensitive local substring match. It still does not explicitly state read-only safety, pagination behavior, or rate/auth constraints, though the read-only nature is strongly implied by 'Discover' and 'Returns'.

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?

The description is three sentences, front-loaded with the core action, and then explains the return contents and the optional filter. Every sentence contributes useful information with no repetition or filler.

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 appropriately enumerates the returned fields and explains the q filtering behavior. It is nearly complete for a simple two-parameter directory tool, with only minor gaps around explicit read-only semantics and pagination.

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 baseline is 3. The description adds useful detail that q is case-insensitive and scoped within the returned category, but it does not add much beyond the already documented q and category parameters.

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 gives a clear verb and resource ('Discover Cricbuzz teams') and specifies that it returns a complete team directory for one category. It distinguishes a directory from team-stat or auction-team siblings, but it does not explicitly name or contrast those alternatives.

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 is implied: use it to retrieve a category's team directory, optionally narrowing by a local name substring. There is no explicit when-to-use versus alternative guidance, such as when to choose cricbuzz_team_stats or cricbuzz_auction_teams instead.

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