Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

thestarmy_headlines

Fetch current headlines and story links from a specified The Star (Malaysia) section, so you can track news by category.

Instructions

Get The Star (Malaysia) section headlines. Returns the current stories of one The Star (Malaysia) section page, usually 10 and up to 100 on column-style sections. section is required, for example news-nation, latest-business, sport-badminton or latest-food. Items have a title and URL, and when the page shows them a type, summary, byline, image and publication time. Older stories are not paginated.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Star (Malaysia) section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return volume (typically 10, up to 100 on column sections), the item shape (title, URL, and conditionally type/summary/byline/image/time), and the important limitation that older stories are not paginated. It omits auth or rate-limit behavior, but the key operational facts are present.

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 purpose, then return volume, then parameter examples, then item shape and the no-pagination caveat. It is dense and every sentence contributes; no filler or repetition.

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, and it does: item fields and the no-pagination constraint are covered. Combined with the single required enum param, an agent has nearly everything needed; only cross-tool routing detail is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with a full enum, so the schema already documents `section` completely. The description reinforces required-ness and adds example slugs, but those examples are already members of the enum, so it adds only marginal value. Baseline 3 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?

States a specific verb (Get) and resource (The Star Malaysia section headlines) and clarifies it returns the current stories of one section page. This is clear, but it makes no explicit distinction from its close siblings thestarmy_news or thestarmy_sections, leaving the agent to infer the boundary.

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?

Usage is only implied: it names the required `section` and gives example slugs, from which one infers this is the tool for a named section. There is no explicit when-to-use vs when-not guidance and no reference to thestarmy_news or thestarmy_sections as alternatives.

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