Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghanaweb_archive_months

List available archive months for GhanaWeb in YYYYMM format with last-updated times, so you can query articles from a chosen month.

Instructions

Discover GhanaWeb archive months. Lists the YYYYMM months currently available in GhanaWeb's article archive, each with the time it was last updated. Use a returned month with the GhanaWeb archive endpoint; the set grows over time. It takes no parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that each entry includes a last-updated timestamp and that 'the set grows over time,' which is useful freshness context, but says nothing about ordering, pagination, or response limits.

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 short sentences, front-loaded with the core action and free of filler. The opening 'Discover GhanaWeb archive months' slightly restates the following sentence, a minor redundancy.

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 zero-parameter discovery tool with no output schema, the description is nearly sufficient: it explains what is returned (months plus update times) and how to chain it into the archive endpoint. It lacks only return ordering/volume detail.

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 the baseline is 4. The description reinforces this with 'It takes no parameters,' leaving no ambiguity that no filtering input is accepted.

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: 'Lists the `YYYYMM` months currently available in GhanaWeb's article archive.' This clearly separates it from content-fetching siblings like ghanaweb_news or ghanaweb_article, though it references the sibling as 'the GhanaWeb archive endpoint' rather than by tool name.

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?

Explicitly tells the agent how to act on the result: 'Use a returned month with the GhanaWeb archive endpoint.' This establishes the discovery-then-fetch workflow. It stops short of stating when NOT to use it or naming alternatives by exact tool name.

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