Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

dailymaverick_news

Retrieve current Daily Maverick articles and opinion pieces with titles, URLs, publication times, summaries, authors, and images, while excluding videos, cartoons, and non-article pages.

Instructions

Get current Daily Maverick stories. Lists recent Daily Maverick articles and opinionista pieces from a rolling set of the newest entries. Each item has its title, URL, type, publication time and, when available, summary, author and image. Videos, cartoons and other non-article pages are excluded.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, the description carries the full burden. It does disclose useful behavior beyond the schema: the item shape (title, URL, type, publication time, and conditional summary/author/image) and what is excluded (videos, cartoons, non-article pages). It says nothing about pagination, result limits, or refresh cadence, so it is adequate but incomplete for a zero-annotation tool.

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?

Three sentences, front-loaded with the core purpose before the item-shape and exclusion details. Every sentence carries information; nothing is boilerplate. Slightly over-elaborated on the return fields, but not wasteful.

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?

With no output schema and no annotations, the description compensates by enumerating the returned fields and the content types filtered out. For a zero-parameter list endpoint this is largely complete, missing only list-level details like pagination or volume.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description adds the relevant caveat that certain fields are only present 'when available'.

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 names a specific verb and resource ('Get current Daily Maverick stories', 'Lists recent Daily Maverick articles and opinionista pieces'), so the agent knows exactly what this returns. It stops short of differentiating itself from the sibling tools dailymaverick_headlines, dailymaverick_sections and dailymaverick_article, leaving the boundaries between them unclear.

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?

There is a scope hint ('rolling set of the newest entries') and an exclusion list, but no explicit when-to-use guidance and no mention of the sibling alternatives. An agent cannot tell from this text why it should pick dailymaverick_news over dailymaverick_headlines or dailymaverick_sections.

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