Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thestarmy_news

Fetch current top stories from The Star (Malaysia) home page as structured items with titles, URLs, section labels, summaries, and bylines.

Instructions

Get The Star (Malaysia) top stories. Returns the current top stories on The Star (Malaysia) home page. It takes no parameters. Each item has a title and canonical URL, plus a short section label in type, a summary and a byline when the page shows them. published_at is omitted here; the section headlines endpoint carries it.

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?

With no annotations the description carries the full burden, and it does well: it enumerates the returned fields (title, canonical URL, `type`, summary, conditional byline) and explicitly flags that `published_at` is omitted. It stops short of discussing rate limits, auth, or pagination, but the output behavior is well disclosed.

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?

Purpose is front-loaded in the first sentence and the field/anomaly notes are tight. The first two sentences restate the same fact (top stories on the home page), which is minor redundancy but not harmful.

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 and no annotations, so the description must explain returns, and it does describe the item fields and one notable omission. Complete enough for a no-parameter home-page tool, though it says nothing about result counts or ordering.

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 the baseline is 4, and the description explicitly confirms 'it takes no parameters', removing any ambiguity for the caller.

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?

Specific verb (Get) plus resource (top stories) plus named source (The Star Malaysia home page). An agent can distinguish it from thestarmy_headlines and thestarmy_sections without opening any schema, since the description pins the exact surface being scraped.

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?

States 'It takes no parameters' and points to the section headlines endpoint as the place to get `published_at`, giving a concrete alternative for that need. It stops short of full when-to-use vs when-not guidance, but the routing hint is clear context.

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