Islam West Africa Collection (IWAC)

Topic distribution

get_topic_distribution

Read-onlyIdempotent

Counts of offline LDA topic assignments, optionally over time. Topic labels are interpretive model outputs; exact topic_id filters select assignments rather than keyword matches. Reports unclassified coverage.

Input 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>.
`top_n`	No	Topics given their own band in over_time (default 8, max 15)
`subset`	No	articles (default) \| references
`country`	No	Exact country name (accents optional)
`date_to`	No
`keyword`	No
`subject`	No	Exact tag
`min_prob`	No	0-1; keep only assignments at or above this probability
`date_from`	No	Inclusive date bounds: YYYY[-MM[-DD]]
`newspaper`	No	Newspaper/periodical substring
`over_time`	No	Also return per-year counts for the leading topics
`hijri_year`	No
`hijri_month`	No
`keyword_mode`	No	literal: the whole keyword as one substring
`keyword_aliases`	No

Output Schema

Name	Required	Description	Default
`note`	No
`span`	No
`view`	Yes
`subset`	Yes
`topics`	Yes
`filters`	Yes
`periods`	No
`classified`	Yes
`total_matches`	Yes
`trend_by_topic`	No
`series_by_topic`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / keyword_mode / description
```
Added value: +"literal: the whole keyword as one substring"
```

Changed14 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; 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"

changedInput schema / properties / subject / description

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

removedInput schema / properties / top_n / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / top_n / minimum
```
Removed value: --9007199254740991
```

Changed2 schema fields changedAug 12, 2026

addedOutput schema / properties / span

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / trend_by_topic

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "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"

AddedJul 28, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description's job is to add data-semantics context, and it does: topic labels are interpretive model outputs (a quality caveat), topic_id filtering operates on assignments not text matches, and results report unclassified coverage. It stops short of describing ordering, defaults, or how subset=references changes output.

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 tight sentences, front-loaded with the core operation before caveats. No filler, though 'Reports unclassified coverage' is terse enough to be slightly ambiguous about whether it is a flag, a count, or a separate section.

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?

For a 15-parameter tool with nested `exact` and an output schema, the description covers purpose and the most surprising semantics but omits how results are grouped/ordered, what subset=references does, and the relationship between top_n and over_time. Adequate but with clear gaps.

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 67%, so the schema carries most parameter documentation. The description adds real meaning for topic_id (exact assignment selection vs keyword match) and implies over_time/top_n behavior, but leaves other parameters like subset, keyword_aliases, and hijri_year unaddressed.

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 ('Counts of offline LDA topic assignments') plus an explicit scope modifier ('optionally over time'). An agent can distinguish it from get_temporal_distribution and get_field_distribution by the LDA-topic subject, though no sibling is named directly.

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?

No statement of when to prefer this over get_field_distribution, get_temporal_distribution, or get_cooccurrence, and no prerequisites. The note that 'exact topic_id filters select assignments rather than keyword matches' clarifies filter behavior but is not usage routing.

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.