Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailymaverick_headlines

Retrieve headlines from a specified Daily Maverick section by slug; returns up to 21 story cards with titles, URLs, summaries, publication times, authors, images, and types.

Instructions

Get headlines from one Daily Maverick section. Returns up to 21 current story cards for one Daily Maverick category. section is required and takes one of 51 slugs such as maverick-news, business-maverick, opinionistas, politics or sport. Each item has its title, URL and type, plus summary, publication time, author and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesDaily Maverick category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the tool returns up to 21 current story cards and lists the item fields, including optional fields, though it does not discuss error behavior, freshness guarantees, or rate limits.

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?

The description is three efficient sentences, front-loads the core action and scope, and then adds return details. Every sentence earns its place.

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?

For a simple one-parameter read tool with no output schema and no annotations, the description provides enough detail about the required input, available sections, and returned item fields. It is nearly complete, though it could mention how section slugs relate to dailymaverick_sections.

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?

The only parameter is required and fully documented in the schema, including an enum of all 51 slugs. The description adds representative examples and confirms the parameter count, but does not contribute syntax or semantics 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?

The description states a specific verb and resource: getting headlines from one Daily Maverick section. It clearly defines scope as a single category, but it does not explicitly differentiate this tool from sibling tools such as dailymaverick_news or dailymaverick_sections.

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 intended usage is implied by the purpose: fetch headlines for one section. However, there is no explicit guidance on when to use this versus dailymaverick_news, dailymaverick_sections, or dailymaverick_article, and no exclusions or alternatives are named.

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