Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

cricbuzz_news_story

Read-only

Use this after discovering a public story URL from cricbuzz_news_topics, cricbuzz_auction_news or another Cricbuzz news page. It returns NewsArticle headline, authors, dates, body, inline links and typed series/team/topic tags for canonical public Cricbuzz story URLs.

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": {
      "url": "<url>"
    },
    "name": "cricbuzz_news_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical public Cricbuzz story URL: https://www.cricbuzz.com/cricket-news/{numeric_id}/{slug}

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.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, and the description adds useful scope: it only handles canonical public Cricbuzz story URLs and returns article content with inline links and typed tags. It does not discuss error behavior for malformed URLs, but the annotations carry the main safety profile.

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, no waste: the usage condition is front-loaded, followed by a compact description of the returned payload. Every sentence contributes needed context.

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?

With one required URL parameter, read-only/open-world annotations, and an output schema present, the description supplies the remaining operational context: where to get the URL and what kind of article data comes back. Nothing essential for correct invocation is missing.

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?

The single URL parameter is fully described in the schema, including the canonical story URL pattern. The description reinforces that it expects a public story URL rather than adding format details beyond the schema, so baseline 3 is appropriate.

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 states a specific resource and return payload: it returns a NewsArticle for a Cricbuzz story URL, including headline, authors, dates, body, links, and tags. This clearly distinguishes it from Cricbuzz listing tools such as cricbuzz_news_topics and cricbuzz_auction_news.

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?

It explicitly says to use this after discovering a public story URL from cricbuzz_news_topics, cricbuzz_auction_news, or another Cricbuzz news page. That establishes both the prerequisite condition and the alternative discovery tools in a single sentence.

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