Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Poems Tagged With A Person

ganjoor_get_person_poems
Read-onlyIdempotent

Retrieve every poem tagged with a given person to discover poetry connected to a historical figure. Supports pagination and returns poem titles and URLs.

Instructions

Get every poem Ganjoor has tagged with a given person.

This is the strongest link between a historical figure and the poetry about them.

Args:

  • person_id (number): Numeric person id

  • 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: { person_id, total, count, page, page_size, has_more, next_page, poems: [{ id, title, full_url }] }

Examples:

  • "Which poems mention this figure?" -> person_id=

Notes:

  • Tagging is curated and incomplete for older figures.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1.
page_sizeNoMaximum items to return per page (1-100, default 20).
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: tagging is curated and therefore incomplete for older figures, plus the paginated envelope (total, count, has_more, next_page) that tells the agent how to iterate. It stops short of saying what the markdown variant looks like.

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 one sentence, followed by clean Args/Returns/Examples/Notes blocks that are easy to scan. The Args section is redundant against a fully described schema, which costs a little, but nothing is padded or vague.

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 compensates by spelling out the JSON return shape and pagination fields, and it flags the coverage caveat in Notes. Only the markdown output format is left unspecified, a minor gap for a read-only list 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 the schema already documents person_id, page, page_size (with 1-100 bounds) and the response_format enum. The Args block largely restates those same constraints without adding format, id-source, or edge-case guidance, so 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 definition opens with a specific verb and resource ("Get every poem Ganjoor has tagged with a given person") and adds a scoping claim ("strongest link between a historical figure and the poetry about them") that separates it from person-centric siblings like ganjoor_get_person_relations or ganjoor_get_person_family_tree. An agent can tell what this returns without opening the schema.

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?

Usage is only implied via a single example question ("Which poems mention this figure?") and the Notes caveat about incomplete tagging for older figures. There is no explicit statement of when to prefer this over alternatives such as ganjoor_search_poems or the other ganjoor_get_person_* tools, so the agent must infer routing.

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