Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indianexpress_sections

List The Indian Express RSS section slugs accepted by the headlines endpoint, including politics, india, explained, cities-mumbai, and lifestyle-health.

Instructions

Get The Indian Express RSS sections. Lists the The Indian Express section slugs that the headlines endpoint accepts, including politics, india, explained, cities-mumbai, entertainment-tamil, lifestyle-health and smart-stocks. Each entry has a slug, a display name and a section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/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. It reveals the return shape (slug, name, url) and confirms these are RSS sections, which implies a safe read. It does not mention rate limits, auth needs, or whether the list is exhaustive, leaving gaps for a no-annotation 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 sentences, each earning its place: purpose, contents plus concrete slug examples, and the return entry structure. The identification of the tool is front-loaded and there is no padding.

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?

With no output schema, the description must describe returns, and it does by enumerating the entry fields (slug, name, url) and giving example slugs. It stops short of stating whether the list is complete or how it relates to other section-listing tools, but it is sufficient to call the zero-param tool correctly.

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 rubric the baseline is 4. There is nothing for the description to disambiguate, and it does not need to compensate for any schema coverage gap.

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 Indian Express RSS sections') and immediately clarifies the payload: the section slugs the headlines endpoint accepts. Naming the headlines endpoint distinguishes it from siblings like indianexpress_news and indianexpress_article without requiring schema inspection.

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 'the slugs that the headlines endpoint accepts', which hints this is a discovery step before calling indianexpress_headlines. However, it never explicitly states when to use this versus alternatives or any prerequisite ordering, so the agent must infer the workflow.

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