Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

timesofindia_news

Fetch current Times of India top stories with titles, URLs, summaries, authors, images, and UTC-offset publication times. Use section or city editions via the headlines endpoint.

Instructions

Get The Times of India top stories. Returns the current Times of India top stories. It takes no parameters. Each item has its title, URL, summary, publication time with its UTC offset, author and image URL. Use the headlines endpoint for a section or city edition.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so the description carries the full behavioral burden. It helpfully discloses that the call takes no parameters and enumerates the returned item fields (title, URL, summary, publication time with UTC offset, author, image URL), which doubles as a mini output contract. However, it says nothing about result count, refresh/freshness, caching, or rate limits — meaningful gaps for a live news feed.

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 and stays short. The first two sentences partially restate each other ('Get ... top stories' / 'Returns the current ... top stories'), which is minor duplication rather than bloat.

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 parameterless fetch with no output schema, the description supplies the essentials: no inputs, the shape of each returned item (including the UTC offset detail), and the routing alternative. Missing only operational details like item count and update cadence.

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, which the description confirms ('It takes no parameters'), so there is nothing for the schema to document and no gap to compensate for. Baseline for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 top stories') and names the sibling endpoint to use for a related but different need. The distinction from timesofindia_headlines is present but thin, since 'top stories' and 'headlines' read as near-synonyms until the routing sentence clarifies the split.

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?

Explicitly routes agents: use this for the default/global top stories, and use the headlines endpoint for a section or city edition. There is no 'when not to use' beyond that, but the primary alternative and its selecting condition are stated.

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