Skip to main content
Glama
Sign In

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

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. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+}
  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. 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
  5. First observed

TDQS

A4.2/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 safety is covered. The description adds genuinely new behavior: OCR is chunked into 25k-character parts and must be followed via next_offset, and keyword mode changes the return shape to excerpts. No info on missing-id behavior or auth.

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?

Two dense sentences with no waste; the primary retrieval behavior is front-loaded, and the pagination and keyword-mode details follow in priority order.

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 no output schema, the description does the necessary work of naming the returned fields and explaining how large payloads are split. Minor gaps remain: what happens when the id doesn't exist, and whether metadata/sentiment are truncated alongside the OCR.

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 80% and already defines offset as the previous part's next_offset and keyword as accent-insensitive excerpt matching. The description mostly restates that; the only real additions are the 25k chunk size and the ~2000-char excerpt size, which is correct but marginal.

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?

Specific verb + resource (get one article by id) plus an enumeration of what comes back: full metadata, AI abstract (description_ai), AI sentiment, OCR text. The by-id single-record framing distinguishes it from search_articles / semantic_search_articles, which return multiple items.

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?

Gives clear operating guidance for pagination ('follow next_offset') and a mode switch: pass `keyword` to trade full OCR for ~2000-char excerpts. It stops short of naming sibling tools (e.g., use search_articles to find an id first), so routing is only implied.

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