Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

news24_sections

Lists the 73 News24 sections accepted by news24-headlines, giving each section's slug, display name, and URL so you can look up valid section paths before requesting headlines.

Instructions

Get News24 sections. Lists the 73 News24 sections accepted by news24-headlines. Each entry has a slug (the URL path under news24.com, which may contain /, as in sport/rugby/springboks), a display name and a page url. Top-level groups include business, life, opinions, southafrica, sport and world.

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 burden and does disclose the entry shape (slug, name, url), the count (73), and the notable edge case that slugs may contain slashes. It omits read-only/auth framing, but for a zero-parameter enumeration tool the disclosure is solid.

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 compact sentences, front-loaded with purpose, then relationship to the sibling, then the entry shape with a concrete example. No filler.

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?

With no output schema and no parameters, the description fully covers what an agent needs: the resource, how it feeds `news24-headlines`, and the structure of each entry including slug edge cases.

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?

Zero parameters, so the baseline is 4. The description instead usefully characterizes the returned fields (slug as a URL path that may contain `/`), which is return-value detail rather than parameter help.

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 ("Get News24 sections") and immediately distinguishes it from the sibling by noting it lists the sections accepted by `news24-headlines`. The scope is unambiguous and sibling-aware.

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?

It clearly frames the tool as the discovery step for `news24-headlines` by stating these are the sections that tool accepts, which implies when to use it. It does not spell out an explicit when-not or a directive ordering, so it stops short of a 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