Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricinfo_news

Retrieve recent cricket news stories with titles, summaries, authors, genres, publication times, images, and match or series IDs. Set an optional limit from 1 to 100.

Instructions

Get latest Cricinfo news. Returns a bounded snapshot of Cricinfo's latest public stories, including titles, summaries, authors, genres, publication times, images, and associated match or series identifiers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cricinfo_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum stories returned, from 1 to 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.2/5.0
Behavior3/5

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

The description does not explain what data will be returned (only 'latest news') or how it will be formatted. It does not mention whether the news will be headlines, summaries, or full articles. The output schema suggests an array of strings (headlines), but this is not communicated in the description, reducing transparency about the tool's behavior.

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?

The description is extremely concise, consisting of a single sentence. It conveys the essential function with no clutter or unnecessary detail.

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

Completeness3/5

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

The description provides the core functionality but lacks details on output structure, potential edge cases, or any constraints (e.g., no mention of pagination, language, or error handling). It is sufficient for basic usage but not comprehensive.

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

Parameters5/5

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

The tool takes no parameters, so there are no parameter descriptions needed. The empty input schema is self-explanatory; there is no potential for parameter misuse or confusion.

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?

The description 'Get latest news from cricinfo' is unambiguous and clearly states the tool's function. It identifies the source (Cricinfo) and the type of content (latest news), leaving no confusion about what the tool does.

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?

The description implies a simple, single-purpose action ('get latest news'), so usage is straightforward. It does not explicitly state that it has no parameters, but the empty input schema indicates that. However, it lacks guidance on how the output should be consumed or any potential variations in behavior.

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