Skip to main content
Glama
Ganjoor MCP Server

Ganjoor MCP Server

Official
by ganjoor

Get Recent Ganjoor Comments

ganjoor_get_recent_comments
Read-onlyIdempotent

Retrieve published Ganjoor reader comments in recency order to review poem discussions, with optional text/user filters and paging, plus Markdown or JSON output.

Instructions

Get the most recent published reader comments across Ganjoor, optionally filtered.

Comments are scholarly notes attached to a specific couplet of a poem.

Args:

  • term (string): Optional text filter applied to comment bodies

  • filter_user_id (string): Optional UUID — only comments by this user

  • 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: { count, page, page_size, has_more, next_page, comments: [{ id, poem_id, poem_title, couplet_index, user, text, date, has_owner_response }] }

Examples:

  • "What are people discussing?" -> no arguments

  • "Comments about 'انتظار'" -> term='انتظار'

Notes:

  • Ordering is by recency, so results change over time — not suitable for questions whose answer must stay stable.

  • Replies are not included, only top-level comments.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1.
termNoOptional substring filter applied to comment text.
page_sizeNoMaximum items to return per page (1-100, default 20).
filter_user_idNoOptional user UUID — only that user's comments.
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 declare readOnly/openWorld/idempotent/non-destructive, and the description adds real context on top: ordering is by recency so results drift over time, and only top-level comments are returned with replies excluded. It also documents the JSON response shape, including has_owner_response and next_page for pagination.

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 one-line purpose followed by clearly labelled Args / Returns / Examples / Notes sections, with each note carrying a distinct fact. Minor redundancy: the Args list duplicates defaults and ranges already present in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully by spelling out the JSON return fields, pagination signals (count, has_more, next_page), the recency-ordering caveat, and the exclusion of replies. An agent has everything needed to call it and interpret results.

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 baseline is 3. The Args block largely restates what the schema already says (term as text filter, page defaults, page_size 1-100, UUID filter); it adds only the mild clarification that the term filter targets comment bodies. No new syntax or edge-case meaning beyond the schema.

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 with scope: "Get the most recent published reader comments across Ganjoor." The follow-up sentence defines what a comment is (a scholarly note attached to a specific couplet), which pins down the object being returned and clearly separates it from poem/person/recitation 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?

Concrete example queries map directly to argument choices (no arguments for "What are people discussing?", term='انتظار' for a topic query), and the Notes section gives an explicit when-not: results are recency-ordered and unsuitable for questions that must stay stable. No named alternative tool is offered, which keeps it from a 5.

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