Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Ganjoor Recitation

ganjoor_get_recitation
Read-onlyIdempotent

Fetch a published recitation by numeric ID to get its audio file URL and poem reference for playback, citation, or metadata lookup.

Instructions

Get one published recitation by its numeric id, including its audio file location and poem reference.

Args:

  • recitation_id (number): Recitation id (from ganjoor_search_recitations or a poem's recitation list)

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

Returns: For JSON: { id, poem_id, poem_title, poem_url, title, artist, artist_url, audio_url, publish_date, duration_seconds, review_status }

Examples:

  • "Details for recitation 37535" -> recitation_id=37535

Notes:

  • Audio URLs point at Ganjoor's CDN and are stable once published.

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": {
      "recitation_id": "<recitation_id>"
    },
    "name": "ganjoor_get_recitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
recitation_idYesNumeric recitation 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds genuinely new context: the "published" qualifier, the stable CDN audio URL note, and the full field list returned in JSON. It omits not-found/error behavior, keeping it below 5.

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 lead sentence front-loads purpose and scope, and the Args/Returns/Examples/Notes structure is easy to scan. The Args section largely repeats schema text and the Returns block omits what markdown output looks like, so a little space is not fully earned.

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 available, the description supplies the JSON return field list, which is the critical missing structured information, plus id provenance and URL stability. For a two-parameter read-only lookup tool, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the baseline is 3; the description earns above baseline by naming the two sources of recitation_id (search results or a poem's recitation list) and giving a concrete worked example. The response_format argument is only restated from the schema, not enriched.

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 gives a specific verb and resource ("Get one published recitation by its numeric id") and immediately scopes the return content (audio file location and poem reference). "One published" distinguishes it from the plural listing siblings like ganjoor_search_recitations and ganjoor_get_poem_recitations without ambiguity.

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 tells the agent where the required id comes from (ganjoor_search_recitations or a poem's recitation list), which is real workflow guidance and prevents wrong-parameter guessing. It does not explicitly state when not to use it or name an alternative for bulk retrieval, so it stops short of a 5.

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