Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

straitstimes_news

Fetch current top stories from The Straits Times as structured JSON, including titles, URLs, summaries, authors, publication times, and images, with no parameters required.

Instructions

Get The Straits Times top stories. Returns the current top stories from The Straits Times. It takes no parameters. Each item has its title, URL and, where the outlet gives them, a summary, author, publication time, image URL and type. Use the headlines endpoint for one section.

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 burden and does disclose the return shape (title, URL, and optional summary, author, publication time, image URL, type) plus the fact that it takes no parameters. It omits auth/rate-limit details, but for a simple read-only news feed this is reasonably transparent.

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 and short, but the first two sentences ('Get The Straits Times top stories' / 'Returns the current top stories from The Straits Times') restate the same idea, so one sentence is not fully earning 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?

No output schema exists, so the description must describe returns, which it does by enumerating the item fields and noting they are conditional on the outlet. Combined with the no-parameter statement and sibling routing hint, it is complete enough for an agent to call 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?

With zero parameters the baseline is 4, and the description reinforces this by explicitly stating 'It takes no parameters,' leaving no ambiguity about the call signature.

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 (Get) and resource (The Straits Times top stories) and explicitly distinguishes itself from the sibling straitstimes_headlines by naming the section-scoped alternative. An agent can differentiate this from the other straitstimes_* tools 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?

Gives a clear usage context (current top stories) and names an alternative endpoint for one-section requests. It does not spell out a full when-not to use this tool, but the routing hint to the headlines endpoint is concrete and actionable.

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