Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailymaverick_sections

List the 51 article-bearing Daily Maverick sections accepted by the headlines tool. Get each category's slug, name, and URL, with empty or media-only categories omitted.

Instructions

List Daily Maverick sections. Lists the 51 article-bearing Daily Maverick categories accepted by dailymaverick-headlines, such as africa, maverick-citizen, op-eds and sci-tech. Each entry has the slug, name and category url. Empty, media-only and other non-story categories are omitted; checked 2026-09-28.

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 provided, so the description carries the full burden, and it does disclose meaningful behavior: 51 entries, included fields (`slug`, `name`, `url`), omitted categories (empty, media-only, non-story), and a checked date. It omits auth, rate-limit, or pagination details, but for a small static read-only list those are minor gaps.

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 core purpose. Each subsequent sentence adds useful detail: the relationship to headlines, example slugs, return fields, omissions, and freshness marker. No filler or repetition.

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 zero-parameter, read-only taxonomy tool with no output schema and no annotations, the description gives enough to call it correctly: what it returns, how many entries, what fields each entry has, which categories are excluded, and how it relates to the headlines endpoint. Nothing essential 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 takes zero parameters and the schema has no properties, so there is no input semantics to explain. The description correctly does not invent parameter guidance; baseline for a zero-parameter tool is 4. It describes output shape instead, which is useful but belongs under behavioral/contextual completeness.

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: 'List Daily Maverick sections.' It further clarifies that these are article-bearing categories accepted by `dailymaverick-headlines`, which distinguishes this taxonomy tool from headline/news/article siblings. Despite using a hyphen where the actual sibling uses an underscore, the purpose is unmistakable.

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?

Provides clear context by tying the output to `dailymaverick-headlines`: these are the categories that endpoint accepts. That implies the tool is for discovering valid section slugs before fetching headlines. It does not explicitly state when not to use it or compare against other Daily Maverick tools, so it falls short of a full 5.

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