Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

ndtv_sections

List NDTV section slugs, display names, and page URLs accepted by ndtv-headlines to find the right category for national, world, city, state, or topic news queries.

Instructions

Get NDTV sections. Lists the NDTV section slugs accepted by ndtv-headlines, each with its display name and page URL. They cover national and world news (latest, india, world), city and state pages such as mumbai-news and kerala-news, and topics such as education and food. spotlight is NDTV's Premium hub; video, podcasts and sister sites are excluded.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 it does describe the return shape (slug, display name, page URL), the scope of coverage (national/world, city/state, topics), and the exclusions plus the 'spotlight' premium caveat. It omits anything about permissions or pagination, but for a static lookup listing that is a minor gap.

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?

Four sentences, front-loaded with the core action and the consumer of the data, with examples of the slug taxonomy kept tight. The opening 'Get NDTV sections' slightly restates the name before the informative second sentence, a small redundancy, but nothing else is wasted.

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?

Despite no output schema and no annotations, the description explains what comes back (slugs, display names, URLs) and what is excluded, which is sufficient for an agent to invoke a zero-arg listing correctly. Additional detail such as ordering or count is not essential here.

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?

The tool takes zero parameters, so per the baseline there is nothing to document and the description cannot add parameter meaning. No parameter-related information is missing or misleading.

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?

States a specific verb and resource ('Get NDTV sections') and immediately specifies the payload: slugs accepted by `ndtv-headlines`, each with display name and page URL. It names a sibling tool explicitly, so an agent can distinguish it from ndtv_headlines/ndtv_news without opening a schema.

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 phrase 'slugs accepted by `ndtv-headlines`' establishes the workflow (call this to discover valid inputs for the headlines tool) and the last clause excludes video, podcasts and sister sites, which is a form of when-not guidance. It stops short of an explicit 'use this before X' directive, so it is clear context rather than a fully spelled-out rule.

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