Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

malaymail_news

Fetch current Malay Mail top stories from its public RSS feed, returning up to 50 headlines, sections, and article routes for archives and story pages.

Instructions

Get Malay Mail top stories. Returns up to 50 current stories from Malay Mail's public all-stories RSS feed. Summaries are publisher teasers, not full article text. Use the sections, headlines, and article routes for verified public archives and story pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses a hard cap (up to 50 stories), the data source (public RSS feed), and that summaries are publisher teasers rather than full article text. Minor gaps remain around freshness/caching and ordering, which for a read-only feed tool is not severe.

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?

Four short sentences, front-loaded with the purpose before the caveats. Every sentence adds a distinct fact (count, source, content type, alternatives); it is efficient, though the closing sentence about routes is slightly dense.

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?

With no output schema and no annotations, the description still tells the agent what comes back (up to 50 current stories), the nature of the text (teasers, not full articles), and where to go for full pages. That covers the essentials for a parameterless feed tool, leaving only ordering/pagination mechanics unstated.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. It correctly offers no parameter guidance because none is needed.

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 and resource ('Get Malay Mail top stories') and identifies the underlying source (public all-stories RSS feed), so the agent knows exactly what is returned. It stops short of explicitly differentiating itself from the sibling malaymail_headlines/malaymail_sections by name, but the scope is unambiguous.

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 final sentence routes the agent to alternatives ('Use the sections, headlines, and article routes for verified public archives and story pages'), which maps to the malaymail_sections, malaymail_headlines and malaymail_article siblings. It gives a clear condition for using those instead, though it never says when NOT to use this feed.

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