Skip to main content
Glama

List poets

gj_poets
Read-onlyIdempotent

Lists classical Persian poets with IDs, nicknames, Hijri life years, and birthplaces, filtered by name or century; returns the first 50 when no query is provided.

Instructions

List poets with ids, nicknames, life years (Hijri) and birthplace, filtered by name or century.

Without a query only the first 50 are shown.

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

Input Schema

NameRequiredDescriptionDefault
eraNoCentury name like 'هشتم' (Hijri century, e.g. 'قرن هشتم').
queryNoPart of the poet's name or nickname, e.g. 'حافظ'.

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, openWorld and non-destructive, so the safety profile is covered. The description still adds real behavioral value by disclosing the truncation rule ('Without a query only the first 50 are shown'), warning the agent that results may be incomplete — though it doesn't say how to page past the cap.

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, no filler. The returned fields come first and the truncation caveat is separated into its own sentence where it reads as a constraint rather than being buried.

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 usefully enumerates the fields returned, which is the main completeness burden for a list tool. The only gap is the absence of any way to retrieve results beyond the first 50 when no query is supplied.

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 documented, including examples ('حافظ', 'هشتم'). The description only restates the two filter axes as 'name or century', adding no format, matching, or combination semantics beyond the schema; 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 gives a specific verb and resource ('List poets') plus the fields returned (ids, nicknames, life years, birthplace) and the two filter axes. It does not name or contrast with the singular sibling gj_poet, so an agent must infer which one to pick, which keeps it 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?

Usage is only implied by the phrase 'filtered by name or century' and by the default-listing behavior. There is no explicit statement of when to prefer this over gj_poet (single poet lookup) or gj_search, and no prerequisites or exclusions are given.

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