Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nationafrica_sections

Retrieve the structured section slugs for Nation Africa’s Kenya edition. Access the slug, display name, and page URL for key content categories like news, politics, and football.

Instructions

Get Nation Africa sections. Lists the 47 section slugs of Nation Africa's Kenya edition accepted by nationafrica-headlines, such as news, politics, counties, football and fact-checks. Each entry has its slug, display name and section page url. Photo, video, audio, puzzle, newsletter and cartoon pages are not included.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 states the exact count, edition scope, returned fields, and explicitly excludes several page types. It does not discuss caching, stability of the 47 slugs, or authentication, but for a simple read-only enumeration tool the key behavioral traits are covered.

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 four sentences, front-loaded with the core purpose and then adding scope, return fields, and exclusions. Every sentence adds useful information and there is no redundant preamble.

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?

Despite having no output schema, the description explains the return shape (slug, name, url), the scope (Kenya edition), the count (47), and exclusions. For a zero-parameter enumeration tool, this is complete enough for an agent to call it correctly and interpret the result.

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 has zero parameters, so the baseline is 4 under the scoring rules. The description does not need to explain parameter semantics and the empty schema is consistent with a no-argument listing operation.

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?

The description gives a specific verb and resource ("Get Nation Africa sections") and immediately narrows scope to the Kenya edition and 47 section slugs. It names the consuming sibling `nationafrica-headlines` and provides concrete examples, so an agent can distinguish this from other `*_sections` tools.

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?

The description clearly links the output to `nationafrica-headlines` by saying these slugs are accepted there, which implies this is the discovery tool for that endpoint. It also excludes photo/video/puzzle/newsletter/cartoon pages, but does not explicitly say "use this before calling headlines" or discuss alternative section-listing tools.

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