Skip to main content
Glama

Poet biography and books

gj_poet
Read-onlyIdempotent

Retrieve a Persian poet's shortened biography and top-level book list by poet ID or URL path, so you can choose a book to open next.

Instructions

A poet's biography (shortened) and the top-level books to open with gj_book.

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

Input Schema

NameRequiredDescriptionDefault
idNoPoet id.
urlNoOr the poet path, e.g. /hafez.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description still adds real value by disclosing that the biography is shortened/truncated and that only top-level books are returned (a hierarchy constraint), but it says nothing about lookup failure behavior, partial matches, or whether id and url can conflict.

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?

Two short sentences with no filler, and the payoff (what you get) is front-loaded before the input instruction. The phrasing is slightly clipped but nothing is wasted.

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 two-optional-parameter read tool with no output schema, the description covers what is returned (shortened bio, top-level books) and how it chains to gj_book, which is sufficient to call it correctly. Only edge-case behavior on invalid identifiers is unaddressed.

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 the '/hafez' path example. "Give id or url" restates the schema's either/or semantics without adding format, precedence, or default-behavior detail beyond it, so this lands at the baseline.

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 the concrete resource set — a shortened poet biography plus the top-level book list — and explicitly ties it to the sibling gj_book for the next step. It is clear an agent gets poet-level data here rather than book or verse content, though the verb is only implied ("biography ... and books").

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" is input guidance, not usage guidance. The mention of gj_book implies this is the entry point before opening a book, but there is no explicit when-to-use versus gj_poets or gj_people, and no statement of what happens if the identifier is unknown.

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