Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Recitation Verse Sync Timing

ganjoor_get_recitation_sync_info
Read-onlyIdempotent

Retrieve per-verse start times for a Ganjoor recitation audio to align text with playback and show when each couplet begins.

Instructions

Get the per-verse timing map for a recitation, showing when each couplet begins in the audio.

Useful for following along with the text while a recitation plays.

Args:

  • recitation_id (number): Recitation id

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

Returns: For JSON: { recitation_id, sync_point_count, total_duration_ms, sync_points: [{ verse_order, text, start_time_ms, start_time_seconds }] }

Examples:

  • "Sync data for recitation 37535" -> recitation_id=37535

Notes:

  • Not every recitation has timing data; an empty list is normal for older uploads.

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_sync_info"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. Beyond that the description adds real behavioral context: not every recitation has timing data, an empty sync_points list is normal for older uploads, and total_duration_ms plus millisecond/seconds dual fields describe what comes back.

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?

Front-loaded with the core meaning in the first sentence, then cleanly sectioned into usage, args, returns, examples and notes. The Args block largely duplicates the schema, which is minor waste, but nothing else is padding.

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?

There is no output schema, and the description compensates by spelling out the JSON return shape including sync_point fields, plus the important 'empty list is possible' caveat. Only the missing prerequisite (where recitation_id comes from) and lack of explicit sibling routing keep it from being complete.

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 100%, with both parameters (including the response_format enum) fully documented in the schema, so baseline 3 applies. The description mostly restates the schema's parameter list and only adds an example value (37535), which is modest marginal value.

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 names a specific verb+resource: a per-verse timing map (couplet start times) for a recitation. It is clearly distinct in substance from a generic recitation-metadata tool, but it never explicitly contrasts itself with the sibling ganjoor_get_recitation or explains that timing is a separate concern from recitation listing.

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?

The line 'Useful for following along with the text while a recitation plays' implies a use case, but there is no explicit when-to-use vs when-not, no mention of the prerequisite that you first need a recitation_id from the recitation lookup, and no named alternative for callers who just want recitation metadata.

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