Skip to main content
Glama

Read a poem

gj_poem
Read-onlyIdempotent

Retrieve a classical Persian poem by ID or ganjoor.net URL, including couplet text, meanings, summary, meter, rhyme, source, and previous/next poem links.

Instructions

Read a poem: text by couplet with meanings, summary, meter, rhyme, source and previous/next poem.

Meanings starting with «هوش مصنوعی:» are AI-written. Give id or url.

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": "gj_poem"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoPoem id.
urlNoOr the ganjoor.net path, e.g. /hafez/ghazal/sh170.
meaningsNoInclude the plain-Persian meaning of each couplet.
max_coupletsNoCouplets to return (80 default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds value beyond that by disclosing the shape of the result and flagging that meanings prefixed with «هوش مصنوعی:» are AI-generated — a real trust signal an agent needs before relaying content. It still omits rate-limit/error behavior and the 80-couplet defaulting effect.

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

Conciseness5/5

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

Two short sentences, front-loaded with the resource and its returned fields, then the AI-content caveat and the required input. Nothing is padded and no sentence is redundant with the name.

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 correctly carries the burden of describing return values, and it does so field by field including previous/next poem. The remaining gaps are minor: precedence between id and url, and truncation behavior when max_couplets caps output.

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 id, url, meanings, and max_couplets are already fully documented with defaults and bounds. The description only reinforces the id-or-url choice and that meanings are included; it adds no format or precedence detail (e.g. what wins if both id and url are given), so 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 names a specific verb and resource ("Read a poem") and enumerates the payload precisely: per-couplet text, meanings, summary, meter, rhyme, source, and adjacent poems. It does not explicitly distinguish itself from siblings like gj_poem_extras or gj_find_verse, so it stops short of a 5.

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?

"Give id or url" tells the agent the invocation contract, which implies this is the direct-by-identifier read path. However, there is no guidance on when to prefer this over gj_poem_extras or gj_find_verse, and no statement about what happens when neither id nor url is supplied.

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