Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

malaymail_article

Retrieve a Malay Mail article by canonical URL and extract structured JSON fields including title, description, authors, body paragraphs, publish times, and paywall status.

Instructions

Get a Malay Mail article. Returns a Malay Mail article by url, an absolute canonical link in the dated form /news/<section>/<year>/<month>/<day>/<slug>/<id>. The response has the title, description, section, authors, lead image, publish and update times, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Malay Mail article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the full response shape (title, description, section, authors, lead image, times, paragraphs, and a paywalled flag), which is useful behavioral context. It stops short of covering error behavior, authentication, or rate limits, so a 3 is appropriate rather than higher.

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?

Two sentences, front-loaded with the core action before moving to URL format and return shape. Every clause carries information and there is no filler, though it could be marginally tighter.

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 itself, and it does so thoroughly, listing every field including the paywalled flag. For a single-parameter fetch tool this is largely complete; only the absence of any usage/routing context keeps it from a 5.

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?

Schema coverage is 100% for the single url parameter, which sets a baseline of 3. The description exceeds that by specifying the exact URL format ('an absolute canonical link in the dated form /news/<section>/<year>/<month>/<day>/<slug>/<id>'), giving the agent concrete guidance the schema's terse 'Canonical Malay Mail article URL' does not.

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 a Malay Mail article.' An agent can immediately tell this fetches a single article, which naturally distinguishes it from sibling feed tools like malaymail_news and malaymail_headlines. However, it never names or contrasts those siblings explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, no alternatives, and no exclusions. It describes what is returned but never tells the agent under what circumstances to pick this tool over malaymail_news or malaymail_headlines, leaving routing to inference from the name alone.

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