Islam West Africa Collection (IWAC)

Semantic scatter

get_semantic_map

Read-onlyIdempotent

Stable-hash sample of matching stored embeddings, projected with PCA. Reports eligible, invalid, missing and capped counts, seed and explained variance. Group counts describe the sample. Coordinates are chart-only; this is not the published UMAP landscape. Needs no API key.

Input Schema

TableJSON Schema

Name	Required	Description
`exact`	No	AND values. Fields: subject/spatial/author/language/country/newspaper/topic_id/min_prob/scored_by; country_raw=whole cell; polarity:<model>.
`limit`	No	Items projected (default 300, max 2000)
`subset`	No	articles (default) \| publications \| references
`country`	No	Exact country name (accents optional)
`date_to`	No
`keyword`	No
`subject`	No	Exact tag
`color_by`	No	country \| newspaper \| subject \| lda_topic_label \| polarity (gpt-5-6-luna's label)
`date_from`	No	Inclusive date bounds: YYYY[-MM[-DD]]
`newspaper`	No	Newspaper/periodical substring
`hijri_year`	No
`hijri_month`	No
`keyword_mode`	No
`keyword_aliases`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`seed`	No
`view`	Yes
`groups`	No
`points`	No
`subset`	Yes
`filters`	Yes
`color_by`	No
`sampling`	No
`projected`	Yes
`limit_warning`	No
`total_matches`	Yes
`requested_limit`	No
`omitted_by_limit`	No
`explained_variance`	Yes
`invalid_embeddings`	No
`missing_embeddings`	No
`eligible_embeddings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedOct 6, 2026

changedInput schema / properties / country / description

Previous value: -"Exact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Nigeria | Togo (accents optional)"New value: +"Exact country name (accents optional)"

changedInput schema / properties / date_from / description

Previous value: -"YYYY-MM-DD (or YYYY)"New value: +"Inclusive date bounds: YYYY[-MM[-DD]]"

removedInput schema / properties / date_to / description
```
Removed value: -"YYYY-MM-DD (or YYYY)"
```

addedInput schema / properties / exact

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 20,
+    "minItems": 1,
+    "type": "array"
+  },
+  "description": "AND values. Fields: subject/spatial/author/language/country/newspaper/topic_id/min_prob/scored_by; country_raw=whole cell; polarity:<model>.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / hijri_month
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / hijri_year
```
Added value: +{
+  "type": "integer"
+}
```

removedInput schema / properties / keyword / description

Removed value: -"ONE French concept keyword; substring over the subset's text fields"

addedInput schema / properties / keyword / minLength
```
Added value: +1
```

addedInput schema / properties / keyword_aliases

Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

addedInput schema / properties / keyword_mode

Added value: +{
+  "enum": [
+    "literal",
+    "all_terms"
+  ],
+  "type": "string"
+}

removedInput schema / properties / limit / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / limit / minimum
```
Removed value: --9007199254740991
```

changedInput schema / properties / newspaper / description

Previous value: -"Newspaper (articles) or periodical/series title (publications)"New value: +"Newspaper/periodical substring"

changedInput schema / properties / subject / description

Previous value: -"Exact subject tag (pipe-aware)"New value: +"Exact tag"

addedOutput schema / properties / eligible_embeddings
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / invalid_embeddings
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / limit_warning
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / missing_embeddings
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / omitted_by_limit
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / requested_limit
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / sampling
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / seed
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedAug 12, 2026

addedOutput schema / properties / groups

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

changedOutput schema / required

Previous value: -[
-  "view",
-  "subset",
-  "filters",
-  "total_matches",
-  "projected",
-  "explained_variance",
-  "points",
-  "note"
-]New value: +[
+  "view",
+  "subset",
+  "filters",
+  "total_matches",
+  "projected",
+  "explained_variance",
+  "note"
+]

Changed1 schema field changedAug 11, 2026

changedInput schema / properties / color_by / description

Previous value: -"country | newspaper | subject | lda_topic_label | polarity (gemini-3-flash-preview's label)"New value: +"country | newspaper | subject | lda_topic_label | polarity (gpt-5-6-luna's label)"

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / color_by / description

Previous value: -"country | newspaper | subject | lda_topic_label | gemini_polarite"New value: +"country | newspaper | subject | lda_topic_label | polarity (gemini-3-flash-preview's label)"

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"

AddedJul 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations cover readOnly/idempotent/openWorld, and the description adds meaningful behavior beyond them: it is a sampled hash projection (not exhaustive), reports eligible/invalid/missing/capped counts plus seed and explained variance, coordinates are chart-only, and no API key is needed. The 'capped' and 'sample' notes are genuinely useful context a caller needs.

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?

Four compact sentences, front-loaded with the projection method and sample semantics, then the disambiguation caveat. No filler; each sentence carries distinct information.

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?

An output schema exists, so return value detail is not required, and the description still flags what the numbers mean (eligible/invalid/missing/capped, explained variance). Given the high parameter count, filter semantics are under-explained, but the core behavioral picture is complete for a charting tool.

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?

With 14 params and 57% schema coverage, the burden is shared. The description adds only loose meaning ('matching', 'capped sample') and does not clarify the many filter params (keyword_mode, keyword_aliases, hijri_*, date_to) left undocumented in the schema. Marginally better than schema-only but not compensating for the coverage gap.

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 operation and output: a stable-hash sample of matching embeddings projected with PCA into a scatter. The scope ('sample', 'chart-only') is clear. It distinguishes itself from a similar published landscape only implicitly via the UMAP contrast, not by naming a sibling tool.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance against the many siblings (get_topic_distribution, get_similar_items, get_cooccurrence, etc.). The description clarifies only the negative boundary ('not the published UMAP landscape') but gives no positive criteria for choosing this tool over alternatives.

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.