Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Ganjoor Person

ganjoor_get_person
Read-onlyIdempotent

Retrieve a person's full profile, including biography, dates, places, and external references, by numeric ID. Use it to identify poets or figures before fetching their poems or relations.

Instructions

Get one person's full record — biography, dates, places, and external references.

Args:

  • person_id (number): Numeric person id (from ganjoor_list_people)

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

Returns: For JSON: { id, name, description, wiki_url, birth_year_hijri, death_year_hijri, birth_location, death_location, family_tree_caption, machine_generated, importance, gender }

Examples:

  • "Who is person 22?" -> person_id=22

Notes:

  • machine_generated marks entries created automatically; their biographies may be sparse.

  • Follow with ganjoor_get_person_poems or ganjoor_get_person_relations for context.

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": {
      "person_id": "<person_id>"
    },
    "name": "ganjoor_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
person_idYesNumeric person 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.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral caveats beyond that, notably that machine_generated entries may have sparse biographies, and it documents the JSON return fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and organized into Args, Returns, Examples, and Notes. Every section contributes useful information without unnecessary filler.

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 appropriately documents the JSON return shape and includes a data-quality note about machine_generated records. It could mention error behavior for missing or invalid person ids, but it is otherwise complete for this simple read tool.

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 both parameters are already documented structurally. The description reinforces person_id's source from ganjoor_list_people and gives an example, but it largely restates schema-provided meaning rather than adding substantial new semantic detail.

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 one person's full record,' and enumerates the record contents (biography, dates, places, external references). This is precise enough to distinguish it from list_people and the person-related sub-tools.

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 clear usage context by noting the person_id comes from ganjoor_list_people and suggests following with ganjoor_get_person_poems or ganjoor_get_person_relations for more context. It lacks an explicit when-not-to-use statement or direct alternative comparison, but the intended invocation path is clear.

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