Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_news_topics

Discover Cricbuzz News sections and topic cards, including IDs, slugs, titles, descriptions, and canonical URLs, with optional substring filtering by title, description, or slug.

Instructions

Discover Cricbuzz News sections and topics. Returns the current public News navigation sections and all topic cards linked from the Topics page, including IDs, slugs, titles, descriptions, and canonical URLs. Topic coverage is dynamic and is discovered from Cricbuzz at request time. The response contains topic metadata only, not story bodies; the Premium Editorials navigation entry is marked premium.

Input Schema

NameRequiredDescriptionDefault
qNoOptional case-insensitive substring search over topic title, description, and slug, up to 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/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 states the response contains IDs, slugs, titles, descriptions, and URLs; that topic coverage is dynamic at request time; that story bodies are excluded; and that Premium Editorials is marked premium. It stops short of explicitly stating read-only behavior or any pagination/rate-limit traits, but the key response semantics are disclosed.

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 front-loaded with the purpose and is appropriately sized. Each sentence adds useful information: return fields, dynamic discovery, metadata-only scope, and the premium marker; there is no filler.

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?

For a simple one-optional-parameter discovery tool with no output schema, the description gives enough detail about return values and dynamic behavior to call it correctly. The only parameter is covered by the schema, and the description fills the output-shape gap that the missing output schema would otherwise leave.

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 optional q parameter is fully documented in the schema (100% coverage), so the schema already explains the substring search semantics. The description never mentions q or how filtered results relate to the claim that 'all topic cards' are returned, which leaves a minor gap but matches the baseline when schema coverage is high.

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?

The description gives a specific verb and resource: discovering Cricbuzz News sections and topics. It clarifies the return shape as News navigation sections plus topic cards, and distinguishes the tool from story-body tools by saying it returns metadata only. However, it does not explicitly differentiate itself from close siblings such as cricbuzz_navigation.

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

Usage Guidelines3/5

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

Usage is implied by 'Discover' and by the metadata-only scope, suggesting this is a browsing/taxonomy step before fetching stories. But there is no explicit when-to-use guidance, no exclusions, and no named alternative tool to route between cricbuzz_news_topics and other Cricbuzz discovery endpoints.

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