Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_cricket_commentary

Fetch Sportskeeda cricket ball-by-ball commentary for a match, returning the current feed and paging older events with a 24-character cursor; language needs a cursor.

Instructions

Get Sportskeeda cricket ball-by-ball commentary. Returns the current commentary feed. To page to older events, pass a 24-character lowercase hexadecimal cursor from an event in /sportskeeda/cricket-match's commentary field (the full feed may contain zero-filled IDs); language then selects an upstream language. The match page's commentary selector offers en, hi, ta, te, and bho. Language without cursor is rejected because the upstream feed ignores it.

Input Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the feed may contain zero-filled IDs, that language is silently ignored upstream without a cursor, and where the cursor originates. It doesn't cover auth, rate limits, or return shape, which keeps it from a 5.

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?

Front-loads the purpose in the first two sentences, then layers in the paging and language rules. It is dense but every sentence carries information; only minor tightening is possible.

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?

Covers parameters and conditional behavior thoroughly for a 3-param read tool with no annotations. The return value is only gestured at ('the current commentary feed') with no output schema to fall back on, leaving a small gap in what the feed contains.

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 3 is the baseline; the description exceeds it by explaining the cursor's provenance (the match page's commentary field), the zero-filled-ID caveat, and the strict dependency of language on cursor. This adds real meaning beyond the schema text.

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?

States a specific verb and resource ('Get Sportskeeda cricket ball-by-ball commentary') and immediately scopes the return ('the current commentary feed'). It implicitly distinguishes itself from provider-agnostic siblings like cricinfo_commentary by naming Sportskeeda, though it doesn't explicitly contrast with sibling tools.

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

Usage Guidelines4/5

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

Gives clear conditional guidance: pass a cursor to page to older events, and language only applies with a cursor. It also explains the constraint that language without cursor is rejected. It stops short of naming alternative tools for different needs, but the when/how is well covered.

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