Skip to main content
Glama

Islam West Africa Collection (IWAC)

by io.github.fmadore
OverviewDiscussionsAdmin

Get article details

get_article
Read-onlyIdempotent

Get one article (by id): full metadata, the AI abstract (description_ai), AI sentiment, and OCR text, in 25k-char parts (follow next_offset). Pass a keyword to get ~2000-char excerpts around each match instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoRead from this character on: the previous part's next_offset
keywordNoReturn excerpts around matches instead of the full OCR (accent-insensitive)
article_idYes
max_excerptsNoDefault 10, max 25
context_charsNoDefault 2000, max 5000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / article_id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / article_id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / context_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / context_chars / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / max_excerpts / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / max_excerpts / minimum
      Removed value: --9007199254740991
    • 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. Changed7 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / article_id / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / context_chars / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / context_chars / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / max_excerpts / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_excerpts / minimum
      Added value: +-9007199254740991
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds real behavioral context beyond them — 25k-char part sizing, the next_offset follow-up pattern, and the ~2000-char excerpt mode. It does not state auth needs or rate limits.

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?

Two dense sentences, front-loaded with the core retrieval action and paging behavior; no filler. Slightly compressed but every clause carries 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?

No output schema, so the description carries return-value burden, which it handles by listing metadata, abstract, sentiment, and OCR text plus the paging contract. Minor gaps remain around excerpt count defaults and error cases.

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 80%, so most parameters are already documented. The description still adds meaning: offset is framed as 'the previous part's next_offset' and keyword is described as producing ~2000-char excerpts around each match, clarifying the interaction between the two parameters.

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 verb and resource ('Get one article') and enumerates the payload ('full metadata, the AI abstract, AI sentiment, and OCR text'), which distinguishes it from search_articles. It stops short of naming siblings explicitly, so not a full 5.

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?

Implies usage via 'by id' and the paging/keyword modes, but never states when to prefer this over search_articles or the other get_* siblings. The keyword-mode condition is clear, but alternative routing is left to inference.

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