Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thestarmy_sections

List The Star (Malaysia) sections that accept headline queries, returning each section's slug, name, and page URL for building news feeds or filters.

Instructions

Get The Star (Malaysia) sections. Lists the 94 The Star (Malaysia) sections that returned at least one story to an anonymous reader when checked on 2026-09-25, and that the headlines endpoint accepts. Examples are news-latest, latest-nation, business-smebiz and sport-football. Each entry has a slug, a name and the section page url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does so reasonably well: it states the list is a snapshot checked on 2026-09-25, is limited to sections that returned at least one story to an anonymous reader, and is accepted by the headlines endpoint. It also discloses the returned fields, though it does not discuss read-only semantics or operational limits.

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?

The description is three focused sentences: the first states the resource, the second gives the selection criteria and examples, and the third describes the return shape. It is front-loaded and every sentence adds useful information without repetition.

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?

Given the low complexity, zero parameters, no annotations, and no output schema, the description is complete enough to use the tool correctly. It provides the count, snapshot date, inclusion criteria, example slugs, and entry fields.

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 has zero parameters, so parameter semantics are not a concern. The description does not need to compensate for any undocumented inputs, and the 4 baseline applies.

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?

The description names a specific verb and resource: "Get The Star (Malaysia) sections." It also quantifies the set as 94 sections and links them to the headlines endpoint, making the purpose clear, though it does not explicitly contrast itself with thestarmy_headlines or thestarmy_news.

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?

The phrase "that the headlines endpoint accepts" implies that these section slugs are useful before calling the headlines tool, but there is no explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions 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