Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

ghanaweb_video_sections

Retrieve the four GhanaWeb TV video categories—news, sports, business, and entertainment—with slugs, display names, and URLs for filtering video searches.

Instructions

Get GhanaWeb TV video sections. Lists the four GhanaWeb TV video categories accepted by ghanaweb-videos: news, sports, business and entertainment. Each entry has a slug, a display name and the category url on GhanaWeb. Takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghanaweb_video_sections"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.7Oct 1, 2026

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 largely meets it: it discloses this is a parameterless static listing and describes the shape of each entry (slug, name, url). It does not explicitly state read-only/non-mutating behavior or that the list is fixed, but for a no-arg lookup 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 short sentences, purpose front-loaded, then the enumerated values, then the return shape. Every sentence adds information an agent needs; nothing is redundant with the (empty) schema.

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, no-output-schema tool the description is complete: it names the resource, enumerates the exact accepted values, and describes the fields of each entry, which is everything needed to call it and to then use ghanaweb_videos.

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, so per the rubric the baseline is 4. The description reinforces this with "Takes no parameters," which is all the parameter guidance that can exist here.

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 GhanaWeb TV video sections") and then enumerates the exact four categories returned, so the agent knows precisely what the payload is. It also names the sibling relationship by saying these are the categories "accepted by `ghanaweb-videos`", distinguishing it from ghanaweb_video(s) and ghanaweb_sections.

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?

By stating the four category values are those accepted by `ghanaweb-videos`, it clearly implies the tool is a discovery/enumeration step to run before calling ghanaweb_videos. It does not, however, explicitly say when not to use it or contrast it with ghanaweb_sections, so guidance is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server