Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nationafrica_news

Fetch top stories from Nation Africa by reading its public news sitemap, returning headlines, publication times, and lead images. Falls back to the News hub if the sitemap is unavailable.

Instructions

Get Nation Africa top stories. Returns the newest Nation Africa (Daily Nation, Kenya) stories from its public news sitemap: headline, publication time and lead image. If the sitemap returns 404, it falls back to the public News section hub, whose relative timestamps may omit publication time. Video pages are excluded.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the data source (public news sitemap), a 404 fallback to the public News hub, that fallback timestamps may be relative and omit publication time, and that video pages are excluded. This is meaningful operational context beyond what a bare name would give.

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 front-loaded sentences that each add information: purpose, source/fields, and fallback/exclusion caveats. No filler, though the "top stories" vs "newest stories" phrasing is slightly loose.

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 parameterless news tool with no annotations and no output schema, the description covers purpose, source, returned fields, fallback behavior, timestamp caveats, and exclusions. About the only gap is distinguishing the tool from its headlines/article siblings.

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?

There are zero parameters, so the baseline is 4. The description instead documents the returned fields (headline, publication time, lead image), which is useful but not a parameter concern.

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+resource ("Get Nation Africa top stories") and scopes it to the newest stories pulled from the public news sitemap. It identifies the publisher (Daily Nation, Kenya) and the returned fields, but does not distinguish itself from close siblings like nationafrica_headlines or nationafrica_article, which an agent must infer.

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?

Usage is implied by "top stories" and the sitemap source, and the fallback path is explained, but there is no explicit when-to-use guidance or naming of alternatives (e.g., nationafrica_headlines, nationafrica_sections) to help the agent choose between them.

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