Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

malaymail_sections

Lists the 11 Malay Mail News sections accepted by malaymail-headlines, including slugs, display names and URLs, so you can choose a valid section before fetching headlines.

Instructions

Get Malay Mail sections. Lists the 11 Malay Mail News sections accepted by malaymail-headlines, from malaysia and singapore to eat-drink, tech-gadgets and what-you-think. Each entry has a slug, display name and section url. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the call takes no parameters and that each entry returns a slug, display name and URL, effectively characterizing a static read-only reference lookup. It does not state read-only/safety explicitly, but the disclosed shape leaves little behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action, then the scope, then the return shape. No filler, no repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless enumeration tool with no output schema, the description covers the resource, the exact number and examples of sections, the return fields, and the absence of inputs. Nothing an agent needs to invoke it correctly is missing.

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 has zero parameters, which sets a baseline of 4. The description reinforces this by stating 'Takes no parameters,' so there is nothing further to document.

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?

States a specific verb and resource ('Get Malay Mail sections') and immediately distinguishes it from the sibling malaymail-headlines. The enumerated examples (malaysia, singapore, eat-drink, tech-gadgets, what-you-think) and the announced return fields (slug, name, url) make the output 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?

Explicitly ties the tool to malaymail-headlines by saying these are the sections that tool accepts, which gives the agent a clear routing signal (fetch sections, then use them). It stops short of stating when NOT to use it or naming other alternatives, so it is clear context rather than full guidance.

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