Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehindu_sections

List valid The Hindu section slugs accepted by the headlines endpoint, covering news, opinion, business, sport, entertainment, education, and food, so you can choose correct query identifiers.

Instructions

Get The Hindu sections. Lists the The Hindu section slugs that the headlines endpoint accepts, covering news, opinion, business, sport, entertainment, sci-tech, education, life and style, society, books and food, for example news-national, sport-cricket and food-recipes. Each entry has a slug, name and url.

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?

No annotations are provided, so the description carries the disclosure burden, and it does so for the essentials: it is a static read-only enumeration of accepted values, and it states the return shape ('Each entry has a slug, name and url'). Auth requirements and rate limits are unstated, but for a parameterless static list those are minor gaps.

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?

Front-loaded with the core action, then details examples and return fields in two supporting sentences. Slightly redundant phrasing ('The Hindu sections' followed by 'the The Hindu section slugs', including the doubled article) costs a fraction of a point but the content is otherwise tight and earns its place.

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?

For a zero-parameter static list with no output schema and no annotations, the description covers what the tool returns (slug/name/url), the domain of values, and the downstream consumer (headlines endpoint). That is sufficient for correct invocation; only auth/rate-limit notes are absent.

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 there is no parameter-level semantics to document; the description appropriately spends its words on the returned entry fields (slug, name, url) instead. Baseline for a 0-param tool applies.

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 The Hindu sections') and directly ties them to a sibling dependency: the slugs 'that the headlines endpoint accepts.' It also enumerates the section taxonomy and gives concrete slug examples, so an agent can distinguish this index tool from thehindu_headlines/thehindu_news without opening any 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 description establishes clear context by stating these are the slugs the headlines endpoint accepts, implying this is the lookup to call before filtering headlines. It does not explicitly say 'call this first' or note any exclusions, but the dependency on the headlines endpoint is a concrete routing signal rather than a guess.

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