Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Ganjoor Poets By Century

ganjoor_get_poets_by_century
Read-onlyIdempotent

Retrieve every poet grouped into historical half-centuries, including featured poets, to identify which poets were active in a specific period.

Instructions

Get every Ganjoor poet grouped into historical half-centuries.

The first group (id 0) holds the "pinned"/featured poets shown on the Ganjoor home page. Each later group carries a name, an approximate Gregorian year range, and the poets active in that period.

Args:

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

Returns: For JSON: { centuries: [{ id, name, start_year, end_year, poet_count, poets: [{ id, name, full_url }] }] }

Examples:

  • "Which poets are from the 14th century?" -> inspect the century entries and their poets

Notes:

  • The whole payload is returned at once; it is a few hundred KB at most.

  • Grouping is editorial, so a poet appears exactly once.

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

Input Schema

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

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description's job is to add context — and it does: the pinned group at id 0, the per-group fields (name, approximate year range, poets), that a poet appears exactly once, and that the entire payload is returned at once at a few hundred KB. It does not discuss ordering of the groups or caching, which are minor gaps.

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?

The structure is well front-loaded — a one-line purpose followed by args, returns, example, and notes. Sections earn their place, though the Args line largely duplicates the schema and the Returns block is somewhat dense.

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?

There is no output schema, and the description compensates by spelling out the JSON return shape and payload size, which is what an agent needs to consume the result. The only shortfall is that group ordering and the markdown format's appearance are not described.

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?

With only one parameter and 100% schema description coverage (including the enum and default), the schema already carries the full meaning. The description restates the argument and its default in the Args block without adding format or behavioral detail beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource plus the organizing dimension: 'Get every Ganjoor poet grouped into historical half-centuries.' That grouping implicitly separates it from a flat poet list such as ganjoor_list_poets, but no sibling is named explicitly, so the differentiation is left for the agent to infer.

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 conveyed only through an example question ('Which poets are from the 14th century?') and a note that the grouping is editorial. There is no explicit statement of when to prefer this over ganjoor_list_poets or ganjoor_get_poet, and no exclusions are given.

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