Islam West Africa Collection (IWAC)

Coverage over time

get_temporal_distribution

Read-onlyIdempotent

Counts by Gregorian or Hijri year/month, or pooled lunar month. Group by country/newspaper. Partial dates and missing lunar dates are disclosed. normalize_by returns numerator counts and per-bucket denominators in the same country/outlet/date scope, removing thematic filters. Shares describe IWAC holdings.

Input Schema

TableJSON Schema

Name	Required	Description
`exact`	No	AND values. Fields: subject/spatial/author/language/country/newspaper/topic_id/min_prob/scored_by; country_raw=whole cell; polarity:<model>.
`subset`	No	articles (default) \| publications \| references \| documents \| audiovisual \| images
`country`	No	Exact country name (accents optional)
`date_to`	No
`keyword`	No
`subject`	No	Exact tag
`calendar`	No	gregorian (default) \| hijri — bucket by the Islamic (Umm al-Qura) calendar
`group_by`	No	country \| newspaper — one distribution per group value
`date_from`	No	Inclusive date bounds: YYYY[-MM[-DD]]
`newspaper`	No	Newspaper/periodical substring
`hijri_year`	No
`granularity`	No	year (default) \| month \| lunar_month (all years collapsed into 12 lunar months; needs calendar=hijri)
`hijri_month`	No
`keyword_mode`	No
`normalize_by`	No	Share per bucket in the same country/outlet/date scope; searchable restricts both counts to full text. Thematic filters are removed from the denominator.
`keyword_aliases`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`view`	Yes
`subset`	Yes
`filters`	Yes
`calendar`	No
`group_by`	No
`dated_count`	Yes
`granularity`	Yes
`denominators`	No
`distribution`	No
`month_labels`	No
`normalize_by`	No
`total_matches`	Yes
`undated_count`	Yes
`invalid_date_count`	No
`denominator_filters`	No
`imprecise_date_count`	No
`distribution_by_group`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 6, 2026

changedInput schema / properties / country / description

Previous value: -"Exact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Nigeria | Togo (accents optional)"New value: +"Exact country name (accents optional)"

changedInput schema / properties / date_from / description

Previous value: -"YYYY-MM-DD (or YYYY)"New value: +"Inclusive date bounds: YYYY[-MM[-DD]]"

removedInput schema / properties / date_to / description
```
Removed value: -"YYYY-MM-DD (or YYYY)"
```

addedInput schema / properties / exact

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 20,
+    "minItems": 1,
+    "type": "array"
+  },
+  "description": "AND values. Fields: subject/spatial/author/language/country/newspaper/topic_id/min_prob/scored_by; country_raw=whole cell; polarity:<model>.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / hijri_month
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / hijri_year
```
Added value: +{
+  "type": "integer"
+}
```

removedInput schema / properties / keyword / description

Removed value: -"ONE French concept keyword (French/English for references); substring over the subset's text fields"

addedInput schema / properties / keyword / minLength
```
Added value: +1
```

addedInput schema / properties / keyword_aliases

Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

addedInput schema / properties / keyword_mode

Added value: +{
+  "enum": [
+    "literal",
+    "all_terms"
+  ],
+  "type": "string"
+}

changedInput schema / properties / newspaper / description

Previous value: -"Newspaper (articles) or periodical/series title (publications)"New value: +"Newspaper/periodical substring"

addedInput schema / properties / normalize_by

Added value: +{
+  "description": "Share per bucket in the same country/outlet/date scope; searchable restricts both counts to full text. Thematic filters are removed from the denominator.",
+  "enum": [
+    "scope",
+    "searchable"
+  ],
+  "type": "string"
+}

changedInput schema / properties / subject / description

Previous value: -"Exact subject tag (pipe-aware)"New value: +"Exact tag"

changedInput schema / properties / subset / description

Previous value: -"articles (default) | publications | references | documents | audiovisual"New value: +"articles (default) | publications | references | documents | audiovisual | images"

addedOutput schema / properties / denominator_filters

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / denominators

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {
+      "type": "number"
+    },
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / invalid_date_count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / normalize_by
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedJul 31, 2026

addedInput schema / properties / calendar

Added value: +{
+  "description": "gregorian (default) | hijri — bucket by the Islamic (Umm al-Qura) calendar",
+  "type": "string"
+}

changedInput schema / properties / granularity / description

Previous value: -"year (default) | month"New value: +"year (default) | month | lunar_month (all years collapsed into 12 lunar months; needs calendar=hijri)"

addedOutput schema / properties / calendar
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / imprecise_date_count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / month_labels

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed2 schema fields changedJul 29, 2026

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"

Changed2 schema fields changedJul 28, 2026

addedOutput schema / properties / view
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "subset",
-  "granularity",
-  "filters",
-  "total_matches",
-  "dated_count",
-  "undated_count"
-]New value: +[
+  "view",
+  "subset",
+  "granularity",
+  "filters",
+  "total_matches",
+  "dated_count",
+  "undated_count"
+]

AddedJul 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive semantics, so the bar is lower. The description still adds real value by disclosing data-quality caveats (partial dates and missing lunar dates are disclosed) and the precise normalize_by behavior (per-bucket denominators, removal of thematic filters from the denominator).

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?

Four sentences, front-loaded with the core counting/bucketing behavior, with no wasted filler. The IWAC-holdings sentence is somewhat jargon-heavy but still purposeful.

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 explained, and the description covers the main temporal axes and normalization. However, with 16 parameters and only 63% schema coverage, filtering options like keyword_mode and the nested 'exact' object remain unexplained, leaving gaps for a complex tool.

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 63%, so the schema carries much of the burden. The description usefully clarifies calendar, granularity (pooled lunar month), group_by, and normalize_by semantics, but leaves several parameters (exact, keyword_mode, keyword_aliases, subset, subject) undocumented in the description text.

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?

The description states a specific operation: counting records bucketed by Gregorian/Hijri year, month, or pooled lunar month, with optional country/newspaper grouping. This clearly identifies it as a temporal-coverage distribution tool distinct from distribution siblings. It does not, however, name any sibling (get_field_distribution, get_topic_distribution, get_country_comparison) to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is implied by the capabilities listed (grouping, bucketing, normalization), but there is no explicit when-to-use/when-not or routing to an alternative. An agent must infer that this is the tool for time-series coverage versus the other get_*_distribution tools.

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) tools Inspect

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.