Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Poem Section

ganjoor_get_section
Read-onlyIdempotent

Retrieve a poem section by its section ID, with optional verses and related sections in markdown or JSON. Use it after mapping IDs with the poem sections tool.

Instructions

Get one section of a poem by its section id, including its verses and its own related sections.

Args:

  • section_id (number): Section id — get these from ganjoor_get_poem_sections

  • include_verses (boolean): Include the section's verses (default: true)

  • include_related (boolean): Include related sections from other poems (default: false)

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

Returns: Section metadata, its metre/rhyme, optionally its verses and its related sections.

Examples:

  • "Show me section 38101" -> section_id=38101

Notes:

  • A section id differs from a poem id; use ganjoor_get_poem_sections first to map between them.

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": {
      "section_id": "<section_id>"
    },
    "name": "ganjoor_get_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
section_idYesSection id from ganjoor_get_poem_sections.
include_versesNoInclude the section's verses.
include_relatedNoInclude sections from other poems related to this one.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds real value by disclosing default values for the optional flags and the section-id-versus-poem-id pitfall that would otherwise cause wrong lookups. It does not discuss result size or how large verse lists behave, so it is not exhaustive.

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 the one-line purpose, then cleanly sectioned into Args/Returns/Examples/Notes. The Args block duplicates the schema's parameter descriptions almost verbatim, which is some waste, but the structure makes the tool scannable.

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 line meaningfully describes the payload: section metadata, metre/rhyme, and the optional verses and related sections. Combined with the id-mapping note, an agent has enough to call it correctly; only return volume/pagination behavior is unaddressed.

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 coverage is 100%, so the schema already documents all four parameters, including defaults and the enum for response_format. The Args block largely restates the schema, adding only the pointer to ganjoor_get_poem_sections for section_id, which the schema also mentions. 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?

States a specific verb and resource ('Get one section of a poem by its section id') and enumerates what comes back (verses, related sections, metre/rhyme). The Notes section explicitly separates it from ganjoor_get_poem_sections (which maps ids) and from poem-level tools, so an agent can tell it apart from siblings.

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 a clear precondition: obtain section_id from ganjoor_get_poem_sections first, and warns that a section id is not a poem id. An example invocation is included. It lacks an explicit when-not statement (e.g., use ganjoor_get_poem_verses for a whole poem), which keeps it below a 5.

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