Crawlora MCP

cricbuzz_teams

Read-only

Returns Cricbuzz's full dynamic team directory for international, domestic, league or women. Use it for the Test and Associate team menus as well as the other listed teams; q searches the returned names locally.

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": {
      "Category": "<Category>",
      "Query": "<Query>"
    },
    "name": "cricbuzz_teams"
  }
}

Input Schema

Name	Required	Description	Default
`Query`	Yes	Optional local substring search over team names, up to 100 characters
`Category`	Yes	Team directory category; defaults to international. Documented values: international, domestic, league, women.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral detail that annotations do not: the search runs locally over the returned names (client-side filtering of the fetched directory), and output schema covers the return shape.

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?

Two sentences, front-loaded with the return value, then the usage and filtering behavior. The trailing clause "as well as the other listed teams" is vague filler, and the "q" abbreviation is a small source of confusion.

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 two-parameter read-only directory tool with a full output schema and full schema coverage, the description covers purpose, category scope, and filter behavior. Missing only explicit sibling routing, which is minor given the completeness of the structured fields.

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 are fully documented there, so the baseline is 3, and the description adds little beyond restating that the query filters names. It also calls the parameter "q" while the schema names it "Query", which is a naming inconsistency rather than useful clarification.

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 ("Returns Cricbuzz's full dynamic team directory") and pins the scope to the four categories the Category param accepts. It is clear what the tool returns, though it never names the obvious sibling (cricinfo_teams) as the alternative source for team lists.

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?

"Use it for the Test and Associate team menus as well as the other listed teams" gives some intended-use context, but it names no alternative tool and no conditions under which this directory should be skipped. The guidance is implied rather than explicit.

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

All Crawlora MCP tools Inspect

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

Need Help?