Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Ganjoor Poet

ganjoor_get_poet
Read-onlyIdempotent

Retrieve a poet’s full profile by numeric ID or URL slug, including biography, birth/death details, and top-level works list; use it to map slugs to IDs or read poet biographies.

Instructions

Get a single poet's full profile (including biography) by numeric id or URL slug.

Use this to turn a slug like "/hafez" into the numeric poet id, or to read a poet's biography and catalogue of works.

Args:

  • id (number): Numeric poet id (optional if url is given). Hafez = 2, Saadi = 7, Rumi = 5.

  • url (string): Poet URL slug such as 'hafez' or '/hafez' (optional if id is given)

  • include_cats (boolean): Include the poet's top-level book/section list (default: true)

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

Returns: Poet profile with id, name, nickname, biography, birth/death (Hijri + places), plus for JSON: { id, name, nickname, biography, birth_year_hijri, death_year_hijri, birth_place, death_place, full_url, cats: [{ id, title, full_url, cat_type }] }

Examples:

  • "Tell me about Hafez" -> url='hafez'

  • "What are Saadi's works?" -> id=7, include_cats=true

Notes:

  • Supply exactly one of id or url. If both are given, id wins.

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

Input Schema

NameRequiredDescriptionDefault
idNoNumeric Ganjoor record id (poet, category, poem, person, ...).
urlNoGanjoor URL slug. Examples: 'hafez/ghazal/sh494', '/hafez/ghazal/sh494', 'mowhaddam/ghazal/ha1'. The leading slash is optional.
include_catsNoInclude the poet's top-level list of books/sections.
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 cover the read-only, idempotent, non-destructive safety profile, so the description's added value is the conflict rule ('If both are given, id wins') and the default for include_cats — genuinely non-obvious behavior. It omits failure behavior for an unknown id/slug, which for an open-world remote lookup would have been worth one line.

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 purpose sentence followed by clearly labeled Usage, Args, Returns, Examples, Notes sections, so an agent can stop reading early. The explicit JSON field enumeration in Returns is somewhat verbose given no output schema exists, but it is not wasted.

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 Returns section usefully describes the shape of the profile, and the optional-parameter defaults and id/url conflict are resolved. The main remaining gap is error or not-found behavior for an invalid identifier.

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 coverage is 100%, so baseline would be 3; the description earns above baseline by supplying domain value mappings (Hafez = 2, Saadi = 7, Rumi = 5) and by clarifying that a leading slash is optional on the slug. The Args block otherwise restates schema text.

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 ('Get a single poet's full profile'), names the two lookup keys (numeric id or URL slug), and notes the biography is included — enough to distinguish it from poem-, category-, or person-oriented siblings without opening a schema.

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 two concrete use cases ('turn a slug like /hafez into the numeric poet id', 'read a poet's biography and catalogue of works') plus worked examples mapping natural-language requests to arguments. It does not name when to prefer a sibling instead, so it stops short of full routing guidance.

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