Islam West Africa Collection (IWAC)

Fetch IWAC item

fetch

Read-onlyIdempotent

Retrieve the full text and metadata of one IWAC item by an id returned from search (format ':', e.g. 'articles:28576'). Returns {id, title, text, url, metadata}: text is the item's OCR / abstract / transcription / description, url is the canonical islam.zmo.de link to cite, and metadata holds the remaining fields (author, date, country, newspaper, AI sentiment, …). Categories: articles, publications, references, documents, index, audiovisual, images.

Input Schema

Name	Required	Description	Default
`id`	Yes	Item id from search, e.g. 'articles:28576' or 'references:11045'

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	No
`text`	Yes
`title`	No
`category`	Yes
`metadata`	Yes
`text_source`	No
`text_truncated`	No
`recommended_tool`	No
`recommended_usage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed1 schema field changedAug 17, 2026
- addedOutput schema / properties / text_source
```
Added value: +{
+  "type": "string"
+}
```

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 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "category": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "metadata": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "recommended_tool": {
+      "type": "string"
+    },
+    "recommended_usage": {
+      "additionalProperties": {},
+      "properties": {},
+      "type": "object"
+    },
+    "text": {
+      "type": "string"
+    },
+    "text_truncated": {
+      "type": "boolean"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "text",
+    "category",
+    "metadata"
+  ],
+  "type": "object"
+}

First observedJul 5, 2026

TDQS

A4.3/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, closed-world behavior, so the bar is lower. The description still adds real value by explaining what `text` contains (OCR/abstract/transcription) and that `url` is the canonical link to cite. It doesn't mention behavior on invalid/missing ids.

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?

Front-loaded with the action and no filler. The first sentence is dense and runs long with parentheticals, but every clause (id format, return shape, field meanings, categories) carries information an agent needs.

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?

With an output schema, full annotation coverage, and a 100%-documented single parameter, the description is nearly complete: it covers sourcing the id, the return payload, and valid categories. The remaining gap is its unresolved relationship to the category-specific get_* siblings and error handling.

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?

Schema coverage is 100% with a single well-documented `id` parameter, so baseline is 3. The description adds the full category enumeration (articles, publications, references, documents, index, audiovisual, images) and the '<category>:<number>' grammar, which goes beyond the schema's two examples.

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 ('Retrieve') and resource ('full text and metadata of one IWAC item') with the exact id format. The 'id returned from `search`' framing makes it distinguishable from the category-specific get_article/get_document/get_reference siblings.

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 anchors usage to ids returned by `search`, which gives a clear workflow context. However, it never says when to prefer this generic fetcher over the category-specific siblings (get_article, get_document, get_image, etc.), leaving the main selection ambiguity unresolved.

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.