Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

straitstimes_sections

List The Straits Times section slugs accepted by the headlines endpoint, including nested categories like singapore/politics, to find valid section paths.

Instructions

Get The Straits Times sections. Lists The Straits Times section slugs that the headlines endpoint accepts, including nested ones such as singapore/politics, asia/east-asia, world/europe, life/food, business/invest, sport/tennis, tech and breaking-news. Each entry has a slug, display name and 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?

No annotations are provided, so the description carries the disclosure burden, and it does useful work: it discloses the return shape ('slug', display 'name', 'url') and warns that slugs can be nested (e.g. 'singapore/politics'). It does not mention auth, rate limits, or ordering, which is a minor gap for a simple read-only listing.

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?

Two tight sentences, front-loaded with the purpose. The slug examples earn their place by demonstrating the nested format an agent will need to construct, rather than padding.

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 zero-param, read-only enumeration tool with no output schema, the description supplies everything needed: what it lists, how slugs are shaped (including nesting), and what fields each entry returns. Nothing an agent needs in order to call it correctly 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?

Zero parameters, so per the rubric the baseline is 4. There is nothing to document, and the description correctly spends no effort on input semantics.

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 Straits Times sections') and immediately ties the output to its consumer: 'section slugs that the headlines endpoint accepts.' An agent can distinguish this from straitstimes_headlines/straitstimes_article without opening a 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 makes the usage context clear by naming the headlines endpoint as the consumer of these slugs, so the agent infers this is a discovery/enumeration step. It stops short of an explicit 'call this before straitstimes_headlines' directive or any when-not guidance, but the routing signal is strong.

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