Skip to main content
Glama

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

NameRequiredDescriptionDefault
exactNoAND values. Fields: subject/spatial/author/language/country/newspaper/topic_id/min_prob/scored_by; country_raw=whole cell; polarity:<model>.
limitNoItems projected (default 300, max 2000)
subsetNoarticles (default) | documents | publications | references
countryNoExact country name (accents optional)
date_toNo
keywordNo
subjectNoExact tag
color_byNocountry | newspaper | subject | lda_topic_label | polarity (claude-haiku-5-5's label)
date_fromNoInclusive date bounds: YYYY[-MM[-DD]]
newspaperNoNewspaper/periodical substring
hijri_yearNo
hijri_monthNo
keyword_modeNoliteral: the whole keyword as one substring
keyword_aliasesNo

Output Schema

NameRequiredDescriptionDefault
noteYes
seedNo
viewYes
groupsNo
pointsNo
subsetYes
filtersYes
color_byNo
samplingNo
projectedYes
limit_warningNo
total_matchesYes
requested_limitNo
omitted_by_limitNo
explained_varianceYes
invalid_embeddingsNo
missing_embeddingsNo
eligible_embeddingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / color_by / description
      Previous value: -"country | newspaper | subject | lda_topic_label | polarity (gpt-5-6-luna's label)"New value: +"country | newspaper | subject | lda_topic_label | polarity (claude-haiku-5-5's label)"
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / keyword_mode / description
      Added value: +"literal: the whole keyword as one substring"
  3. Changed1 schema field changed
    • changedInput schema / properties / subset / description
      Previous value: -"articles (default) | publications | references"New value: +"articles (default) | documents | publications | references"
  4. Changed22 schema fields changed
    • 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"
      +}
  5. Changed2 schema fields changed
    • 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"
      +]
  6. Changed1 schema field changed
    • 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)"
  7. Changed1 schema field changed
    • 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)"
  8. Changed2 schema fields changed
    • 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"
  9. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower. The description adds real value: deterministic stable-hash sampling, returned counts/seed/explained variance, and the caveat that coordinates are chart-only and not the published UMAP layout. It does not address the sampling cap behavior or what 'invalid/missing' mean operationally.

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?

Four tight sentences, front-loaded with the mechanism and followed by output contents and the key caveat. Dense but every sentence carries information; minor cost from compressed phrasing like 'Group counts describe the sample.'

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, the description needn't enumerate return fields, yet it usefully summarizes them (eligible/invalid/missing/capped, seed, explained variance). Annotations cover safety. Only gap is that filter parameters and subsetting semantics are left entirely to the schema.

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 coverage is 64% across 14 parameters with a nested 'exact' object, so the schema carries most of the semantic load. The description mentions 'matching' and 'Group counts' but adds no detail on filters, limit caps, or subset/color_by behavior beyond what the schema already documents.

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 concrete mechanism: stable-hash sampling of stored embeddings projected with PCA, and explicitly names what it is not ('not the published UMAP landscape'). An agent can tell this apart from semantic_search_* siblings, though the phrase 'semantic map' itself remains loosely defined.

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?

Usage is implied rather than stated: 'Coordinates are chart-only' signals a visualization/exploration use case, and 'Needs no API key' removes a barrier. There is no explicit when-to-use-this-vs-semantic_search_articles guidance or statement of exclusions beyond the UMAP disclaimer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.