Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

List Ganjoor People

ganjoor_list_people
Read-onlyIdempotent

Lists historical and literary figures catalogued as related persons in Ganjoor, with optional name search and pagination, for finding people referenced in poem commentary.

Instructions

List the historical and literary figures Ganjoor has catalogued as related persons (شخصیت‌ها).

These are people who appear in a poem's commentary or annotations — rulers, prophets, companions, poets' contemporaries — as distinct from poets themselves.

Args:

  • search (string): Optional filter — only people whose name contains this text

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

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

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

Returns: For JSON: { total, count, page, page_size, has_more, next_page, people: [{ id, name, birth_year_hijri, death_year_hijri, birth_location, death_location, importance, gender }] }

Examples:

  • "Who does Ganjoor know about?" -> no arguments

  • "Find the person named 'حافظ'" -> search='حافظ'

Notes:

  • Filtering is done client-side; the full list is a few hundred entries.

  • importance ranks how central the person is; higher means better documented.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1.
searchNoCase-insensitive substring filter on the person's name.
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.2/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 openWorld, so safety is covered. The description adds genuinely new behavioral context: filtering happens client-side over a corpus of a few hundred entries, and the `importance` field ranks documentation depth. It does not discuss pagination edge behavior, but the shape is disclosed in the Returns block.

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 purpose and scope, then organized into Args / Returns / Examples / Notes, which is easy to scan. The Args section largely duplicates a fully-covered schema and could be dropped without loss, which keeps it from a 5.

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, and the Returns block fully specifies the JSON payload and pagination fields, so nothing return-related is missing. Corpus scale, client-side filtering, and the meaning of `importance` round out what an agent needs to call and interpret this tool correctly.

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 all four parameters are already documented in the schema. The Args section restates page, page_size and response_format nearly verbatim and adds no syntax or format detail beyond what the schema provides; only the note that search is a substring filter loosely mirrors the schema's own wording. Baseline 3 applies.

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 ('List the historical and literary figures Ganjoor has catalogued as related persons') and then explicitly scopes it against poets, which is the closest sibling (ganjoor_list_poets). The parenthetical Persian term and the concrete examples of who counts (rulers, prophets, companions, contemporaries) make the resource unambiguous.

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?

Usage is clearly implied by the two examples ('Who does Ganjoor know about?' with no arguments vs. a name lookup via search) and by the explicit distinction from poets. It stops short of naming alternatives such as ganjoor_get_person for retrieving a single person's details, so an agent must infer that boundary itself.

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