Skip to main content
Glama
Sign In

Islam West Africa Collection (IWAC)

by io.github.fmadore
OverviewDiscussionsAdmin

Newspaper statistics

get_newspaper_stats
Read-onlyIdempotent

Per-newspaper article counts and date ranges.

Input Schema

NameRequiredDescriptionDefault
countryNoExact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Togo (accents optional)

Output Schema

NameRequiredDescriptionDefault
viewYes
newspapersYes
country_filterNo
total_articlesYes
total_newspapersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / view
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "total_newspapers",
-  "total_articles",
-  "newspapers"
-]New value: +[
+  "view",
+  "total_newspapers",
+  "total_articles",
+  "newspapers"
+]
  4. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "country_filter": {
+      "type": "string"
+    },
+    "newspapers": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_articles": {
+      "type": "number"
+    },
+    "total_newspapers": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_newspapers",
+    "total_articles",
+    "newspapers"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the result is an aggregate of counts plus date ranges, which is genuine behavioral context, but it says nothing about scope (whole corpus vs. filtered) or ordering of the returned newspapers.

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?

One front-loaded sentence fragment with no filler, and the key output notion is stated up front. It is efficient but borders on under-specification given a filterable, aggregating tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still missing is the optional country filter and whether the default is the whole corpus, which an agent needs in order to pick between this and get_country_comparison.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single country parameter is fully documented in the schema with its allowed values and accent tolerance. The description never mentions the country filter, adding nothing beyond the schema; baseline 3 applies.

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 the resource (per-newspaper statistics) and the two metrics returned (article counts and date ranges), which is more specific than the title alone. It does not differentiate from near-siblings such as get_collection_stats or get_country_comparison, so the agent must infer the newspaper-level granularity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer for corpus-wide or country-level stats. The only hint that it is newspaper-level comes from the word 'per-newspaper' in the description text.

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

All Islam West Africa Collection (IWAC) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources