Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

List Ganjoor Metres (Rhythms)

ganjoor_list_rhythms
Read-onlyIdempotent

Lists Persian prosodic metres in the Ganjoor corpus with IDs, verse patterns, and poem counts, helping you find the metre ID needed for rhythm analysis or similar-poem searches.

Instructions

List every Persian prosodic metre (وزن) used in the Ganjoor corpus, with its verse-pattern notation.

Use this to translate a metre name into the id Ganjoor uses, or to discover the metre vocabulary before calling ganjoor_find_similar_poems or ganjoor_analyze_poem_rhythm.

Args:

  • page (number): Page number, starting from 1 (default: 1)

  • page_size (number): Items per page, 1-100 (default: 50)

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

Returns: For JSON: { count, page, page_size, has_more, next_page, rhythms: [{ id, rhythm, verse_count }] }

Examples:

  • "What metres exist?" -> no arguments

  • "Find the metre 'فاعلاتن'" -> page through results looking for the pattern

Notes:

  • rhythm is the classical Persian scansion pattern; verse_count is how many Ganjoor poems use it.

  • There are roughly 50-70 metres; one page of 100 usually covers everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ganjoor_list_rhythms"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1.
page_sizeNoMaximum items to return per page (1-100, default 20).
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.3/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; the description still adds real context beyond that: the return payload shape, the fact that the corpus holds roughly 50-70 metres, and the meaning of rhythm vs verse_count. It stops short of auth or rate-limit disclosure, but none is implied for a static reference list.

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?

Purpose is front-loaded in the first two sentences, then Args/Returns/Examples/Notes in a scannable order. The Examples section is somewhat redundant with the usage sentence, and the Notes restate the return fields, so it is slightly longer than needed.

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 carries the return contract and does so well (count/page/has_more/next_page/rhythms). The only incompleteness is the page_size default mismatch against the schema, which leaves the agent with two conflicting values for a non-required parameter.

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%, so page, page_size and response_format are documented in the schema and the baseline is 3. The description repeats the ranges but introduces a conflict: it states page_size 'default: 50' while the schema default is 20, which could mislead an agent reading only the prose. It adds no syntax or semantics beyond the schema otherwise.

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?

States a specific verb and resource ('List every Persian prosodic metre used in the Ganjoor corpus'), plus what each entry carries ('verse-pattern notation'). The second sentence distinguishes it from ganjoor_find_similar_poems and ganjoor_analyze_poem_rhythm by naming them as downstream consumers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two explicit use cases ('translate a metre name into the id Ganjoor uses' and 'discover the metre vocabulary before calling...') and names the sibling tools that follow. It also sets the expectation that lookup requires paging ('page through results looking for the pattern'), so an agent knows how to execute, not just when.

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