Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofindia_sections

Lists all 55 Times of India sections, including national, world, business, cricket, and city editions, with slugs, display names, and feed URLs for the headlines endpoint.

Instructions

Get The Times of India sections. Lists the 55 Times of India sections that the headlines endpoint accepts, covering national and international topics such as india, world, business and cricket, and India city editions such as mumbai, delhi and bangalore. Each entry has a slug, a display name and the section feed url.

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 must carry the behavioral load, and it does reasonably well: it discloses this is a bounded enumeration (55 entries) covering topical and city-edition sections, and describes the shape of each entry. It does not mention read-only status explicitly, but the static lookup nature is evident from 'lists'.

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 tightly packed sentences: what it is, what it contains (with concrete examples of slug categories), and what each entry yields. No filler and the most decision-relevant facts are front-loaded.

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 parameterless list endpoint with no output schema, the description supplies everything needed: the count, the category coverage, example slugs, and the per-entry fields (slug, name, url). Nothing an agent needs in order to call or use the result 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. The description adds useful context by documenting the example slug values an agent would pass downstream, which compensates for the absence of any schema properties.

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 Times of India sections') and quantifies the payload ('55 sections'). It distinguishes itself from siblings like timesofindia_headlines and timesofindia_news by framing the output as the set of section identifiers the headlines endpoint accepts.

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 'that the headlines endpoint accepts' tells the agent this is a discovery/enumeration tool to run before calling a headlines endpoint. However, it does not explicitly say when to prefer this over a direct headlines call or name a concrete sibling alternative, so the routing guidance is implied rather than spelled out.

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