Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indiatoday_sections

List the 35 India Today sections accepted by indiatoday-headlines, returning each section's slug, display name, and URL so you can pick valid identifiers.

Instructions

Get India Today sections. Lists the 35 India Today sections accepted by indiatoday-headlines, such as top-news, south-india, markets, ott, elections and history-of-it. Each entry has a slug, display name and the section page url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 delivers: it discloses the result cardinality (35 sections), concrete example values, the exact shape of each entry (slug, name, url), and that no input is required. It never explicitly says the call is read-only, which is the only notable omission for a pure reference tool.

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?

Three tight sentences, front-loaded with the purpose, then the key linking fact, then the return shape. No filler and nothing an agent would need to skim past.

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 no-parameter reference lister with no output schema, the description supplies everything needed: what is returned, what fields each entry contains, how many entries, and sample values. Nothing required to call or consume it correctly is missing.

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 the baseline is 4, and the description reinforces this with 'Takes no parameters,' removing any doubt. There are no parameters whose semantics need further explanation.

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 India Today sections') and immediately distinguishes itself from the sibling indiatoday_headlines by declaring it enumerates the sections that tool accepts. An agent can tell this is a reference/lookup endpoint, not an article or news fetch.

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 link to `indiatoday-headlines` tells the agent exactly when this tool is relevant: discovering valid section identifiers before querying headlines. It does not spell out an explicit 'use this when / not when' rule or name a competing sections tool, so it stops short of a 5.

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