Skip to main content
Glama

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

TableJSON 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. 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"
+}
  2. 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"
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive), yet the description adds substantial behavior beyond them: transcription paging at 25k-char parts with next_offset, keyword excerpts as an alternative, source_type as the signal for which link applies, and which of the three URLs is the citation-grade one.

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?

Front-loads verb+resource, then packs return fields and link disambiguation into compact clauses, closing with pagination/keyword behavior. Every sentence carries information an agent cannot get from the schema or annotations; no filler.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, including the ambiguous three-URL case and transcription truncation. An agent has enough to call correctly and interpret the response without guessing.

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% (only offset is documented in the schema), so the description must compensate. It does: 'keyword returns excerpts instead' defines the otherwise-bare keyword param, and 'follow next_offset' clarifies the offset semantics. audiovisual_id is self-evident from 'by id', leaving only minor gaps.

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?

States a specific verb and resource ('Get one audiovisual record by id') and then enumerates the actual fields returned (description, transcription, creator/channel, duration, medium, subjects, places, language, rights, source, and the three link types). This lets an agent distinguish it from list_audiovisual/search_audiovisual purely on the 'by id, single record' scope.

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?

Clearly establishes the trigger context ('by id') and explains two invocation variants within the tool: paginating a long transcription via next_offset and using 'keyword' to get excerpts instead of the full part. It does not name a sibling tool to route away to, so it stays short of a full 5.

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