Islam West Africa Collection (IWAC)

Get document details

get_document

Read-onlyIdempotent

Get one archival document (by id): full metadata, AI description, and OCR text, in 25k-char parts (follow next_offset). Pass a keyword to get ~2000-char excerpts around each match instead, useful for long documents.

Input Schema

TableJSON Schema

Name	Required	Description
`offset`	No	Read from this character on: the previous part's next_offset
`keyword`	No	Return excerpts around matches instead of the full OCR (accent-insensitive)
`document_id`	Yes
`max_excerpts`	No	Default 10, max 25
`context_chars`	No	Default 2000, max 5000

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 6, 2026
- removedInput schema / properties / context_chars / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / context_chars / minimum
```
Removed value: --9007199254740991
```
- removedInput schema / properties / document_id / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / document_id / minimum
```
Removed value: --9007199254740991
```
- removedInput schema / properties / max_excerpts / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / max_excerpts / minimum
```
Removed value: --9007199254740991
```
- addedInput schema / properties / offset
```
Added value: +{
+  "description": "Read from this character on: the previous part's next_offset",
+  "type": "integer"
+}
```

Changed1 schema field 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"

Changed7 schema fields changedJul 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / context_chars / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / context_chars / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / document_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / document_id / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / max_excerpts / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / max_excerpts / minimum
```
Added value: +-9007199254740991
```
First observedJul 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real behavioral context beyond them: the 25k-character chunking, the follow-`next_offset` paging protocol, and the keyword-mode excerpt behavior. It doesn't address auth needs or edge/error cases, keeping it just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences that are front-loaded with the primary behavior (fetch one document by id) followed by the alternative mode. No filler or redundancy.

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 no output schema, the description carries the return-value burden and does so by naming the returned fields and the pagination mechanism. It is nearly complete for a read-only getter, though it omits error/not-found behavior and explicit auth expectations.

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 already 80%, so baseline is 3. The description goes further by explaining that offset should be set to the previous part's next_offset and by characterizing keyword mode's excerpt semantics, adding meaning beyond the schema 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 verb and resource ('Get one archival document (by id)') and enumerates the payload (metadata, AI description, OCR text), which is far more informative than a tautology. It does not explicitly name or contrast against close siblings like get_article or get_publication_fulltext, so it stops short of full sibling differentiation.

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?

It gives clear conditional guidance for the keyword path ('Pass a keyword to get ~2000-char excerpts... useful for long documents'), which implies when to use it. However, there is no explicit when-to-use/when-not guidance relative to sibling retrieval tools such as search_documents or get_article.

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.

Get document details

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources