Islam West Africa Collection (IWAC)

Collection statistics

get_collection_stats

Read-onlyIdempotent

Overall statistics for every IWAC subset, including fulltext_coverage — how many items in each subset actually carry searchable full text in this dataset. Read that before treating any keyword count as a full-text census.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_collection_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`view`	Yes
`date_range`	No
`dataset_url`	Yes
`fulltext_note`	No
`subset_counts`	Yes
`total_records`	Yes
`failed_subsets`	No
`collection_name`	Yes
`newspaper_count`	No
`fulltext_coverage`	No
`articles_by_country`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

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

addedOutput schema / properties / view
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "collection_name",
-  "dataset_url",
-  "subset_counts",
-  "total_records"
-]New value: +[
+  "view",
+  "collection_name",
+  "dataset_url",
+  "subset_counts",
+  "total_records"
+]

Changed2 schema fields changedJul 27, 2026

addedOutput schema / properties / fulltext_coverage

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / fulltext_note
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "articles_by_country": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "collection_name": {
+      "type": "string"
+    },
+    "dataset_url": {
+      "type": "string"
+    },
+    "date_range": {
+      "additionalProperties": {},
+      "properties": {
+        "earliest": {
+          "type": "string"
+        },
+        "latest": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "earliest",
+        "latest"
+      ],
+      "type": "object"
+    },
+    "failed_subsets": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "newspaper_count": {
+      "type": "number"
+    },
+    "subset_counts": {
+      "additionalProperties": {
+        "type": "number"
+      },
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "total_records": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "collection_name",
+    "dataset_url",
+    "subset_counts",
+    "total_records"
+  ],
+  "type": "object"
+}

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 declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds real semantic context beyond them: what fulltext_coverage means and the interpretive caveat about keyword counts. It doesn't mention cost or output shape, but the output schema covers shape.

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 tight sentences, zero waste. The core purpose is front-loaded and the caveat follows as the actionable detail.

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 present and no parameters, the description only needs to justify existence and flag interpretation pitfalls — it does both. The remaining gap is the lack of explicit routing to sibling tools for different statistics.

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?

Zero parameters, so baseline 4 applies. There's nothing for the description to document and it doesn't waste space pretending otherwise.

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+resource: 'Overall statistics for every IWAC subset', which distinguishes it from the metric-specific siblings like get_lexical_metrics and get_newspaper_stats by being the aggregate overview. It doesn't explicitly name an alternative, so it falls short of 5.

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?

The second sentence implies when the output matters ('Read that before treating any keyword count as a full-text census'), giving a concrete decision context. However, there's no explicit when-to-use-this-vs-sibling guidance among the many search/distribution tools.

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.