Islam West Africa Collection (IWAC)

Search IWAC

search

Read-onlyIdempotent

Search the Islam West Africa Collection across newspaper articles, Islamic publications, archival documents, academic references, audiovisual recordings, photographs, and the authority index (persons/places/organisations/events/subjects). Pass ONE concept or name — e.g. 'Tijaniyya', 'laïcité', 'Sheikh Gumi', 'pèlerinage'. Matching is accent- and case-insensitive; a multi-word query requires every word to appear somewhere in the item, so prefer a single concept per call. Write query strings and concept keywords in French for press/publication/document/index discovery even when the user's report language is not French. Academic references are multilingual, so try French and English title/abstract terms when relevant; metadata/filter labels remain French. Use the French transliteration of Islamic terms (Tabaski not 'Eid al-Adha', charia not 'sharia', Maouloud not 'Mawlid'). Returns {results:[{id,title,url,category}], ranking}; each result's category names its subset and the ranking field documents the ordering. Pass an id to fetch to read the full text. For filtered queries (by country, date, or newspaper) use the search_* tools instead.

Input Schema

Name	Required	Description	Default
`limit`	No	Max results across all categories. Default 20, max 50.
`query`	Yes	One concept, name, or short phrase; use French concept terms for primary sources, and French/English terms for references

Output Schema

Name	Required	Description	Default
`count`	Yes
`limit`	Yes
`ranking`	Yes
`results`	Yes
`deep_scan`	Yes
`limit_warning`	No
`requested_limit`	No
`search_coverage`	No
`coverage_warning`	No
`unavailable_categories`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed9 schema fields changedOct 6, 2026
- removedInput schema / properties / limit / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / limit / minimum
```
Removed value: --9007199254740991
```
- removedOutput schema / properties / count / maximum
```
Removed value: -9007199254740991
```
- removedOutput schema / properties / count / minimum
```
Removed value: --9007199254740991
```
- removedOutput schema / properties / limit / maximum
```
Removed value: -9007199254740991
```
- removedOutput schema / properties / limit / minimum
```
Removed value: --9007199254740991
```
- removedOutput schema / properties / requested_limit / maximum
```
Removed value: -9007199254740991
```
- removedOutput schema / properties / requested_limit / minimum
```
Removed value: --9007199254740991
```
- addedOutput schema / properties / search_coverage
```
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"

Changed2 schema fields changedJul 27, 2026

addedOutput schema / properties / deep_scan
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "results",
-  "count",
-  "limit",
-  "ranking"
-]New value: +[
+  "results",
+  "count",
+  "limit",
+  "ranking",
+  "deep_scan"
+]

Changed2 schema fields changedJul 26, 2026
- addedOutput schema / properties / coverage_warning
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / unavailable_categories
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed5 schema fields changedJul 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / limit / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / limit / minimum
```
Added value: +-9007199254740991
```

changedInput schema / properties / query / description

Previous value: -"One concept, name, or short phrase (French for press; French/English for scholarship)"New value: +"One concept, name, or short phrase; use French concept terms for primary sources, and French/English terms for references"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "limit": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "limit_warning": {
+      "type": "string"
+    },
+    "ranking": {
+      "type": "string"
+    },
+    "requested_limit": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "category"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results",
+    "count",
+    "limit",
+    "ranking"
+  ],
+  "type": "object"
+}

First observedJul 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral detail beyond them: accent- and case-insensitive matching, conjunctive multi-word semantics, the {results, ranking} shape, and the category/ranking fields. It stops short of stating result caps behavior or latency, but for a read-only search tool that is a minor gap.

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?

Purpose and the one-concept rule are front-loaded, and nearly every sentence carries operational value. The language/transliteration block is slightly verbose and repeats the French-instruction idea, so it is helpful but not maximally tight.

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?

Covers retrieval scope, query construction rules, language conventions, return structure (despite an output schema existing), and the follow-up tool. Nothing an agent needs to call this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but the description goes far beyond: it dictates French query language for primary sources, French+English for references, French transliteration conventions (Tabaski, charia, Maouloud), and single-concept phrasing. That is directly actionable semantics the schema does not convey.

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 (Search) plus the exact corpus and enumerates the subsets covered (articles, publications, archives, references, audiovisual, photos, index). It also disambiguates from the search_* siblings by scope, so an agent can distinguish it from search_articles or search_index without opening a schema.

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

Usage Guidelines5/5

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

Explicitly instructs to pass ONE concept and explains why (multi-word queries AND all terms), names the alternative for filtered use ('For filtered queries ... use the search_* tools instead'), and describes the fetch handoff by id. When-to-use, when-not-to-use, and alternatives are all present.

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.