Skip to main content
Glama

Poems with same meter and rhyme

gj_similar
Read-onlyIdempotent

Find poems that share a given meter and rhyme, returning their first couplet with pagination. Use it to locate verse with matching rhythm and rhyme from Ganjoor.

Instructions

Find poems that share a meter and rhyme, with their first couplet; 10 per page.

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": {
      "meter": "<meter>"
    },
    "name": "gj_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
meterYesMeter id or name (part of it is enough if unique), from gj_meters.
cat_idNoOnly this book/category.
poet_idNoOnly this poet.
rhyme_lettersNoRhyme letters, e.g. 'ارا' (poem.rhyme_letters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavioral detail: results include the first couplet and come 10 per page. However, it leaves the match semantics unclear — it says 'meter and rhyme' while rhyme_letters is optional, so it is ambiguous whether rhyme must also match, and it says nothing about result ordering.

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?

A single compact sentence with the matching criterion front-loaded, the return content second, and pagination last. Nothing is wasted and nothing needs to be read twice.

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 5-parameter, one-required, read-only lookup with no output schema, the description covers what is returned and how results are paged, which is the main gap such tools usually have. The remaining hole is the similarity/ordering semantics and whether rhyme filtering is mandatory, which an agent would want before choosing this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds information the schema lacks: a page yields exactly 10 results, which clarifies the meaning of the page parameter. It does not explain the meter id-vs-name resolution or rhyme_letters format, which the schema already handles.

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?

States a specific verb and resource ('Find poems') plus the matching criterion ('share a meter and rhyme'), which is far more informative than the title alone. It also previews the return payload ('their first couplet') and page size. It does not explicitly contrast itself with siblings like gj_search or gj_poem, 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?

The description implies when the tool is useful (you want poems sharing a meter/rhyme) but never states when to prefer it over gj_search, gj_find_verse, or gj_poem, nor any preconditions. Guidance is implied rather than explicit.

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