Islam West Africa Collection (IWAC)

Research workbench

explore_corpus

Read-onlyIdempotent

Selection workbench: items, concordance, coverage, compare (requires comparison), attention, aliases, or paginated manifest/CSL-JSON/BibTeX exports. Exact filters intersect. limit/offset also page compare/coverage/attention cells. Coverage measures archive availability. Exports identify this page and dataset snapshot; compare snapshot IDs across pages. Schema discovery: iwac://datasets/{subset}.

Input Schema

Name	Required	Description	Default
`link`	No	Export modes: link the whole selection (≤5000) as one file instead of a page
`mode`	No		items
`limit`	No
`offset`	No
`subset`	No		articles
`selection`	No
`comparison`	No

Output Schema

Name	Required	Description	Default
`mode`	No
`note`	No
`rows`	Yes
`view`	Yes
`limit`	No
`export`	No
`offset`	No
`subset`	Yes
`filters`	Yes
`metrics`	No
`overlap`	No
`has_more`	No
`temporal`	No
`selections`	No
`total_cells`	No
`source_field`	No
`omitted_cells`	No
`total_matches`	Yes
`source_exact_field`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / comparison / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / comparison / properties / keyword_mode / description
```
Added value: +"literal: the whole keyword as one substring"
```
- addedInput schema / properties / link
```
Added value: +{
+  "description": "Export modes: link the whole selection (≤5000) as one file instead of a page",
+  "type": "boolean"
+}
```
- addedInput schema / properties / selection / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / selection / properties / keyword_mode / description
```
Added value: +"literal: the whole keyword as one substring"
```
Changed1 schema field changedOct 27, 2026
- addedOutput schema / properties / total_cells
```
Added value: +{
+  "type": "number"
+}
```
AddedOct 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 behavior. The description adds useful behavioral context beyond those annotations: exact filters intersect, coverage measures archive availability, exports identify the page and dataset snapshot, and snapshot IDs can be compared across pages.

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?

The description is dense but front-loaded, starting with the workbench purpose and mode list before moving to behavioral details. It is appropriately sized for a multi-mode tool, though the telegraphic phrasing occasionally makes it harder to parse.

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?

This is a complex tool with nested selection/comparison objects and low schema coverage, and an output schema exists so return values need not be explained. The description covers several invocation-relevant behaviors, but gaps remain around the 'link' parameter, individual filter fields, and mode defaults.

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 description coverage is only 14%, so the description must compensate. It clarifies mode categories, limit/offset behavior for certain modes, the required comparison for compare mode, and exact-filter intersection, but it omits important semantics such as the 'link' export option and details of several selection fields.

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 identifies a specific multi-mode selection workbench and enumerates its modes (items, concordance, coverage, compare, attention, aliases, exports), giving a clear sense of what the tool does. It does not explicitly compare itself to the large set of search/get/list siblings, but the mode list distinguishes it as a broader selection and export surface.

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 some operational guidance, such as 'compare (requires comparison)' and that limit/offset page compare/coverage/attention cells. However, it does not state when to use this tool instead of search_* or get_* siblings, nor does it describe when not to use particular modes.

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.