Skip to main content
Glama

Poem recitations, replies and comments

gj_poem_extras
Read-onlyIdempotent

Retrieve recitations with MP3 links, manuscript images, songs, related and quoting poems, and reader comments for a poem ID; choose which extras to include.

Instructions

Recitations with mp3 links, manuscript images, songs, related poems, quoting poems and reader comments.

Each part is trimmed (about 10 items).

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

Input Schema

NameRequiredDescriptionDefault
idYesPoem id (`id` from search or book results).
partsNoWhich extras: recitations, images, songs, related, quoted, comments. Default recitations+related.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive open-world operation. The description adds valuable behavioral context by listing what is returned and warning that each part is trimmed to about 10 items, though it does not discuss pagination or full-result retrieval.

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?

The description is two compact sentences that front-load the returned content and then note the truncation behavior. Every sentence adds useful information with no wasted wording.

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 read-only extras-fetching tool with complete parameter documentation and no output schema, the description covers the main return categories and the important per-part trimming limit. It could be slightly more complete about response structure, but it gives an agent enough to call the tool correctly.

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 the required poem id and optional parts list are fully documented in the schema. The description restates the parts that can be requested but does not add syntax, defaults, or per-parameter behavior beyond the schema.

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 clearly identifies the resource as poem extras and enumerates the returned sections: recitations, images, songs, related poems, quoted poems, and comments. It is specific but does not explicitly distinguish this from sibling tools such as gj_poem or gj_recitations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. The implied use case is visible from the name and contents, but the agent must infer when this tool should be chosen over siblings.

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