Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

cricbuzz_team_stats

Read-only

Returns one team stats table. First call cricbuzz_team_stats_options for the same team/category; stat, format_id, year and opponent_id must exactly match discovered values.

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>",
      "TeamID": "<TeamID>",
      "Stat": "<Stat>",
      "FormatID": "<FormatID>",
      "Year": "<Year>",
      "OpponentID": "<OpponentID>"
    },
    "name": "cricbuzz_team_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
StatYesA value returned for the selected team by /cricbuzz/team/stats/options; current India values are mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties, mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr
YearYesYear value returned by /cricbuzz/team/stats/options, including all when offered
TeamIDYesTeam ID returned by /cricbuzz/teams for the selected category
CategoryYesTeam-directory category from /cricbuzz/teams. Documented values: international, domestic, league, women.
FormatIDYesFormat ID returned by /cricbuzz/team/stats/options
OpponentIDYesOpponent ID returned by /cricbuzz/team/stats/options, including all when offered

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

A4.6/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 the important behavioral constraint that values are not free-form but must echo a prior discovery call, which prevents guessing. It stops short of anything about the shape or bounds of the returned table, but the output schema covers that.

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, zero filler: the return statement comes first and the prerequisite/constraint second. Nothing repeats the name or the schema.

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 six-required-parameter, prerequisite-gated tool with an output schema and readOnly annotations, the description covers the essential dependency chain. Minor gap: it does not restate that Category/TeamID come from cricbuzz_teams, though the schema descriptions already say so.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all six parameters are already documented with their source endpoints (teams, team/stats/options). The description still adds value by stating the exact-match provenance rule across stat/format_id/year/opponent_id, telling the agent these are copied tokens rather than invented values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ('Returns one team stats table') and implicitly separates itself from cricbuzz_team_stats_options by casting the latter as the discovery step. An agent can tell which of the two cricbuzz stats tools to call last without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the workflow: call cricbuzz_team_stats_options first for the same team/category, then pass stat, format_id, year and opponent_id exactly as discovered. This is a genuine when/how-to-call instruction rather than an implied one.

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