Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Poem Manuscript Images

ganjoor_get_poem_images
Read-onlyIdempotent

Retrieve manuscript and facsimile images for a given poem ID, with thumbnail and full-resolution links to check textual variants against the source.

Instructions

Get the manuscript and facsimile images Ganjoor holds for a poem.

These are photographs of the physical manuscripts, with a thumbnail and a full-resolution link per image — useful for checking a textual variant against its source.

Args:

  • poem_id (number): Numeric poem id

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON: { poem_id, image_count, images: [{ id, url, thumbnail_url, alt, description }] }

Examples:

  • "Show the manuscript for poem 2623" -> poem_id=2623

Notes:

  • Most poems have no images; an empty list is the normal case.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "poem_id": "<poem_id>"
    },
    "name": "ganjoor_get_poem_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
poem_idYesNumeric poem id.
response_formatNoOutput format: 'markdown' for human-readable text (default) or 'json' for machine-readable structured data.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful non-annotation context: the payload is a list of images with per-image thumbnail and full-resolution URLs, and empty results are the common case rather than an error. It does not cover pagination or absolute image counts, but the net contribution beyond annotations is solid.

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?

The key statement is front-loaded in the first sentence, and the Args/Returns/Examples/Notes structure makes scanning easy. Some duplication between the prose and the Args list is unavoidable, but the sections each carry distinct information. Slightly longer than strictly needed, yet no sentence is 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?

There is no output schema, so the Returns section is essential and the description supplies it fully with field-level detail. Combined with the empty-list caveat, the example invocation, and the explanation of what the images represent, an agent has everything needed to call this correctly and interpret results.

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 description coverage is 100%, so both parameters are already documented in the schema, and the Args block largely restates those descriptions verbatim. The only addition is a worked example mapping ('poem 2623' -> poem_id=2623). Baseline 3 is appropriate when the schema carries the load.

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 opens with a specific verb and resource ('Get the manuscript and facsimile images ... for a poem') and clarifies what those images actually are (photographs of physical manuscripts with thumbnail and full-res links). That distinguishes it from the many other poem_* sibling endpoints, though it never names an alternative explicitly. Unambiguous about what the tool returns.

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?

It gives a concrete motivating use case ('useful for checking a textual variant against its source') plus an important expectation-setter ('Most poems have no images; an empty list is the normal case'). It stops short of stating when NOT to call it or pointing to a different tool for related needs, so it lacks the exclusion language a 5 requires.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.