Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

iol_headlines

Fetch recent IOL headlines for a specified section path, such as news or sport/rugby/springboks, returning titles, URLs, summaries, times, images, and authors.

Instructions

Get IOL section headlines. Returns recent IOL headlines for one section path. section is required and takes a value such as news, news/south-africa/gauteng, sport/rugby/springboks, business/economy or entertainment/music. Each item has its title, URL, summary, publication time and image, plus the author when the outlet names one. Unlisted values are rejected.

Input Schema

NameRequiredDescriptionDefault
sectionYesIOL section path

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 behavioral burden. It usefully discloses the return shape (title, URL, summary, publication time, image, author when present) and the strict enum rejection behavior, but says nothing about pagination, result limits, caching, or authentication.

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, front-loaded sentences that move from purpose to parameter to return shape to constraint, with no filler. Minor redundancy in re-listing example section paths already captured by the enum.

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 appropriately describes the item fields an agent will receive. With one fully documented enum parameter and the return shape covered, the definition is complete enough to invoke correctly; only pagination/limits are unaddressed.

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 single parameter is a fully enumerated string, so the schema already does the heavy lifting. The description restates the concept and repeats example values that are already present in the enum, adding a clarification of the path format but little beyond the schema.

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 IOL section headlines... Returns recent IOL headlines for one section path'), which is clear and actionable. It does not explicitly distinguish itself from siblings like iol_article or iol_sections, but the scope ('one section path') 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 Guidelines3/5

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

The description implies when to use it by requiring a section path and warning that unlisted values are rejected, and it names concrete example paths. However, it never states when to prefer this over iol_article, iol_news, or iol_sections, so alternative-selection guidance is left to inference.

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