Skip to main content
Glama
Sign In

Islam West Africa Collection (IWAC)

by io.github.fmadore
OverviewDiscussionsAdmin

Get audiovisual details

get_audiovisual
Read-onlyIdempotent

Get one audiovisual record by id: full description and transcription (where one exists), creator/publishing channel, duration, medium, subjects, places, language, rights, source, and three distinct links: url (the IWAC page, the one to cite), external_url (where a harvested video plays) and media_url (a deposited file). source_type says which to expect. A long transcription comes in 25k-char parts (follow next_offset); keyword returns excerpts instead.

Input Schema

NameRequiredDescriptionDefault
offsetNoRead from this character on: the previous part's next_offset
keywordNo
audiovisual_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed4 schema fields changed
    • removedInput schema / properties / audiovisual_id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / audiovisual_id / minimum
      Removed value: --9007199254740991
    • addedInput schema / properties / keyword
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Read from this character on: the previous part's next_offset",
+  "type": "integer"
+}
  3. 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"
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this as a safe read-only, idempotent operation; the description adds valuable behavioral detail beyond that. It explains the three link types and their meanings, clarifies `source_type`, and discloses that long transcriptions are returned in 25k-character parts with `next_offset`.

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?

The description is dense but front-loaded and every clause carries useful retrieval context. The field enumeration, link distinctions, and pagination note are all relevant and efficiently packed into two sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return content; it does so thoroughly. It covers the record fields, the three URL variants, source-type behavior, and transcription pagination, leaving little ambiguity for an agent invoking it.

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 only 33%, so the description must compensate. It clarifies that `keyword` returns excerpts rather than full transcription and that pagination follows `next_offset`; the required `audiovisual_id` is obvious from 'by id'. It could be more explicit about passing `offset` as the pagination parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get one audiovisual record by id.' It immediately distinguishes this retrieval-by-id operation from list/search siblings and enumerates the record content an agent can expect.

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

Usage Guidelines4/5

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

Usage is clear from 'by id' and from the note that `keyword` returns excerpts instead of full transcription. It also explains pagination via `next_offset`. It does not explicitly name search_audiovisual or list_audiovisual as alternatives for finding an id, so it falls short of full when-to-use routing.

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