Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_cricket_commentary

Read-only

Get Sportskeeda ball-by-ball commentary by match slug. Page older commentary with a 24-character cursor from sportskeeda_cricket_match's commentary field (the full feed may have zero-filled IDs); discover language options with sportskeeda_page_options.

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": {
      "slug": "<slug>"
    },
    "name": "sportskeeda_cricket_commentary"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesHost-free match path returned by /sportskeeda/schedule
cursorNoNonzero 24-character lowercase hexadecimal commentary ID from /sportskeeda/cricket-match commentary
languageNoOlder-comment language; valid only with cursor. Documented values: en, hi, ta, te, bho.

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. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Nonzero 24-character lowercase hexadecimal commentary ID from /sportskeeda/cricket-match commentary"
    • addedInput schema / properties / language / description
      Added value: +"Older-comment language; valid only with cursor. Documented values: en, hi, ta, te, bho."
    • addedInput schema / properties / slug / description
      Added value: +"Host-free match path returned by /sportskeeda/schedule"
  2. First observed

TDQS

A4.7/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, so safety is covered. The description adds genuinely useful operational context absent from annotations: the cursor's origin, its 24-character form, and the caveat that the full feed may contain zero-filled (invalid) IDs. It does not describe pagination limits or result shape, but the output schema covers 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?

Two dense sentences, front-loaded with the verb+resource, then the pagination mechanics and the discovery pointer. No filler; every clause carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All three parameters are documented in the schema, an output schema exists for returns, and annotations cover the safety profile. The description supplies the cross-tool workflow (cursor provenance, language discovery) that an agent needs to actually call it correctly, so nothing material is missing.

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 description coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining where the cursor comes from, warning that zero-filled IDs are unusable, and directing language discovery to sportskeeda_page_options - real semantics the schema alone does not convey.

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 specific verb ('Get'), resource ('ball-by-ball commentary'), and source ('Sportskeeda'), plus the keying parameter ('by match slug'). It is clearly distinguishable from the many sibling commentary/score tools by naming the exact content type and provider.

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 describes the pagination workflow ('Page older commentary with a 24-character cursor from sportskeeda_cricket_match's commentary field') and routes discovery of language options to sportskeeda_page_options. It names the two related sibling tools and the field that supplies the cursor, so the agent knows how to proceed without guessing.

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