Skip to main content
Glama

Islam West Africa Collection (IWAC)

by io.github.fmadore
OverviewDiscussionsAdmin

Search audiovisual materials

search_audiovisual
Read-onlyIdempotent

Search audiovisual materials by keyword and metadata: francophone web video from Burkina Faso, Togo and Benin (TV reports, association and campus recordings), plus deposited Nigerian Hausa/Arabic recordings. Keyword matches title, creator, publisher, subject, spatial, language, source, the item's own description (the richest text most of these items have) and its transcription where one exists. Each row says which population it is from (source_type) and carries either external_url (a video to watch) or media_url (a file), never both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoDefault 20, max 50
mediumNoExact carrier medium: Vidéo sur le web | DVD | CD (validated, accents optional)
offsetNo
countryNoExact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Nigeria | Togo (accents optional). Burkina Faso, Togo, Benin and Nigeria only — no Niger or Ivorian items
keywordNoSubstring match across audiovisual title/metadata fields
subjectNoExact subject tag — only ~27 rows carry one, so prefer publisher/keyword
languageNoExact language value, e.g. Français | Haoussa | Arabe | Anglais | Mooré
publisherNoSubstring on the publishing channel/broadcaster, e.g. RTB | AEEM | CERFI
source_typeNoyoutube (harvested web video, the large majority) | deposited (recordings with a file, 47)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / limit / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / offset / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / offset / minimum
      Removed value: --9007199254740991
  2. Changed3 schema fields changed
    • addedInput schema / properties / publisher
      Added value: +{
+  "description": "Substring on the publishing channel/broadcaster, e.g. RTB | AEEM | CERFI",
+  "type": "string"
+}
    • addedInput schema / properties / source_type
      Added value: +{
+  "description": "youtube (harvested web video, the large majority) | deposited (recordings with a file, 47)",
+  "type": "string"
+}
    • changedInput schema / properties / subject / description
      Previous value: -"Exact subject tag"New value: +"Exact subject tag — only ~27 rows carry one, so prefer publisher/keyword"
  3. Changed3 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). The subset is currently all Nigeria"New value: +"Exact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Nigeria | Togo (accents optional). Burkina Faso, Togo, Benin and Nigeria only — no Niger or Ivorian items"
    • changedInput schema / properties / language / description
      Previous value: -"Exact language value, e.g. Haoussa | Arabe | Anglais"New value: +"Exact language value, e.g. Français | Haoussa | Arabe | Anglais | Mooré"
    • changedInput schema / properties / medium / description
      Previous value: -"Exact medium: audio | video (validated)"New value: +"Exact carrier medium: Vidéo sur le web | DVD | CD (validated, accents optional)"
  4. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  5. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Exact country name (the subset is currently all Nigeria)"New value: +"Exact country name: Benin | Burkina Faso | Côte d'Ivoire | Niger | Nigeria | Togo (accents optional). The subset is currently all Nigeria"
    • changedInput schema / properties / medium / description
      Previous value: -"Exact medium: audio | video"New value: +"Exact medium: audio | video (validated)"
  6. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, closed-world, non-destructive, so the bar is lower. The description adds real value beyond them: the full list of fields keyword matches (including the item's own description and transcription) and the guarantee that each row carries either external_url or media_url, never both.

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?

Purpose is front-loaded in the opening clause, then detail follows. Sentences are dense but each earns its place by conveying searchable-field and return-shape information; slightly long but not padded.

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?

A read-only search tool with zero required params and no output schema. The description compensates by describing populations, searchable fields, and row structure. Complete enough to call correctly, with only alternative-routing guidance left out.

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 89%, so the baseline is 3. The description enriches keyword semantics by enumerating the matched fields beyond the schema's generic 'title/metadata', and clarifies source_type as two populations (youtube majority vs 47 deposited records), adding meaning over the schema.

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 gives a specific verb+resource (search audiovisual materials) and details the exact populations covered (Burkina Faso/Togo/Benin web video, deposited Nigerian Hausa/Arabic recordings). It distinguishes itself from generic siblings by content, though it never explicitly names alternatives like search_documents or get_audiovisual.

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, when-not-to-use, or alternative routing is provided. The population description implies the tool's scope but gives no conditions or guidance on choosing it over the many search_* siblings.

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) toolsInspect
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.

Resources