Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghanaweb_sections

List the 15 GhanaWeb article sections accepted for headline queries, with each section's slug, name, and URL. Excludes video and non-article areas.

Instructions

Get GhanaWeb article sections. Lists the 15 article sections GhanaWeb accepts for ghanaweb-headlines, from news and sports to tabloid, lifestyle and features. Each entry has a slug, display name and section url. Video and other non-article areas are left out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.1/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 burden and does disclose the shape of the result (slug, display name, url), the fixed count (15), and the deliberate exclusion of video/non-article areas. It does not state auth needs or that the operation is a pure read, though for a static enumeration that omission is low-risk.

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 short sentences, front-loaded with the action and scope, then the field list, then the exclusion. Every sentence carries information and none is redundant.

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, no annotations and zero parameters, the description supplies what an agent needs: the resource, the count, the return fields and the exclusion boundary. Minor gaps (ordering, whether the list is stable) are negligible for this tool class.

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; baseline is 4. It correctly spends no words on non-existent inputs.

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 and resource (list GhanaWeb article sections) and pins the scope to the 15 sections accepted by `ghanaweb-headlines`. It implicitly separates itself from `ghanaweb_video_sections` by saying video and non-article areas are left out, but never names that sibling explicitly, so it stops short of full differentiation.

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?

Clear context: the sections are the valid inputs for `ghanaweb-headlines`, which tells an agent to call this first to discover valid slugs, and it excludes video/non-article areas. It does not name the alternative tool to use for those excluded areas, so guidance is strong but not complete.

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