Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_cricket_match

Fetch a Sportskeeda cricket match center using a schedule slug to get public scorecards, innings, teams, squads, player data, and live commentary; betting fields are excluded.

Instructions

Get a Sportskeeda cricket match center. Returns the public scorecard, innings, teams, squads, player data, and latest commentary for a cricket match slug discovered from /sportskeeda/schedule. Betting fields are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesHost-free match path returned by /sportskeeda/schedule

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses what is returned and that 'Betting fields are excluded', but says nothing about read-only nature (implied by 'Get'), pagination, or freshness/live-vs-final state of the match center.

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 verb and resource, and every clause adds information (payload contents, slug source, betting exclusion). No 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?

For a single-parameter read tool with no output schema or annotations, the description adequately conveys what the agent gets back and where the input comes from. Minor gaps around live/final data state and pagination keep it from a 5.

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 the single slug parameter is fully documented in the schema. The description restates the same origin ('/sportskeeda/schedule') without adding syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 clear verb and resource ('Get a Sportskeeda cricket match center') and enumerates the payload (scorecard, innings, teams, squads, player data, commentary). It does not explicitly differentiate itself from close siblings like cricinfo_match or sportskeeda_cricket_commentary, but the source reference and betting-field exclusion give it a distinct scope.

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?

It clearly indicates where the required slug comes from ('discovered from /sportskeeda/schedule'), which is the prerequisite an agent needs. It stops short of naming alternatives or when-not-to-use conditions, so it is clear context without explicit routing.

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