Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

malaymail_headlines

Fetch current Malay Mail section headlines by section slug, returning each headline title and URL for news monitoring.

Instructions

Get Malay Mail section headlines. Returns current Malay Mail headline cards for one News section. section is required and takes one of malaysia, singapore, money, world, life, eat-drink, showbiz, opinion, sports, tech-gadgets or what-you-think. Each item has its title and URL; no summary, author, time or image is returned.

Input Schema

NameRequiredDescriptionDefault
sectionYesMalay Mail News section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 full burden and does useful work by disclosing the return shape: each item has only a title and URL, and explicitly no summary, author, time or image. That prevents an agent from assuming richer metadata. It omits any auth, rate-limit or freshness/pagination behavior, which keeps it from a 5.

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?

The purpose is front-loaded in the first sentence and the sentences are short. The full eleven-value slug list is redundant with the schema and inflates the length, which is the one clear efficiency cost.

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?

There is no output schema, so the description must characterize returns, and it does so by naming the returned fields and the notable omissions. Combined with the enum coverage, an agent has what it needs to call it. Freshness/count of headlines is not addressed, which is a minor gap.

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% and the enum is already fully defined in the schema, so the description's enumeration of all eleven slugs largely duplicates structured data rather than adding meaning. It confirms `section` is required and scopes it to one value at a time, which is marginally useful. 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?

The description states a specific verb and resource: 'Get Malay Mail section headlines' and clarifies it returns 'headline cards for one News section.' That is enough to separate it from malaymail_article (single article) in spirit, but it never names a sibling or explicitly contrasts itself with malaymail_sections or malaymail_news, so it stops short of full differentiation.

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 scope statement 'for one News section' implies the tool is for section-level browsing, but there is no explicit when-to-use guidance, no mention of when to prefer malaymail_news or malaymail_article, and no prerequisites or exclusions. Usage must be inferred from the single required parameter.

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