Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Resolve Ganjoor Page Id To URL

ganjoor_get_page_url
Read-onlyIdempotent

Resolve a Ganjoor page ID for a poem, category, or poet into its public web URL path, so you can cite or link the item from a bare numeric ID.

Instructions

Resolve any Ganjoor page id (poem, category, or poet) to its public web URL path.

Useful when you have a bare numeric id from an index or a citation and need to cite or link it.

Args:

  • id (number): Any Ganjoor page id — poem, category, or poet

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

Returns: For JSON: { id, url, full_url }

Examples:

  • "What is the link for id 13836?" -> id=13836

Notes:

  • Ids are globally unique across poems, categories and poets on Ganjoor.

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": {
      "id": "<id>"
    },
    "name": "ganjoor_get_page_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage id to resolve. Works for poems, categories, and poets.
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/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), lowering the bar. The description still adds real behavioral context beyond them: ids are globally unique across poems, categories and poets, and the JSON return shape is { id, url, full_url }. Minor gap: the markdown return format is not described.

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

Conciseness3/5

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

The opening sentence and usage line are front-loaded and earn their place, as do the Returns and Notes sections. However, the Args block duplicates the schema verbatim, and the Examples section adds little beyond the already-clear single-parameter usage, making the definition longer than necessary.

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?

For a two-parameter read-only lookup with no output schema, the description covers purpose, trigger, return shape (JSON) and the global-id invariant well. It would be complete at 5 if it also described the markdown return format, since no output schema exists to fall back on.

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 both parameters are already fully documented, and the Args block essentially restates the schema. The only added meaning is the note that ids are globally unique across page types, which reinforces the 'any id' semantics. 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 opens with a specific verb+resource+output: 'Resolve any Ganjoor page id (poem, category, or poet) to its public web URL path.' It clearly distinguishes this lookup/normalization function from siblings like ganjoor_get_poem_by_id, which fetch content rather than URLs.

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?

It gives a clear triggering condition: 'Useful when you have a bare numeric id from an index or a citation and need to cite or link it.' This is a solid when-to-use signal. It does not explicitly name any sibling tool (e.g., ganjoor_get_redirect_url) as the alternative or state when not to use it, so it falls short of a 5.

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