Skip to main content
Glama

Hafez faal or random poem

gj_faal
Read-onlyIdempotent

Draw a Hafez faal or a random Persian poem and read it with meanings.

Instructions

Draw a Hafez faal (a random ghazal of Hafez) or, with random=True, a random poem, read with meanings.

Same output as gj_poem.

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

Input Schema

NameRequiredDescriptionDefault
randomNoTrue for a random poem (any poet) instead of a Hafez faal.
poet_idNoWith random: only this poet (2 is 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, openWorld and non-destructive, so safety behavior needs no restating. The description adds that results come 'read with meanings' and that output matches gj_poem, which is useful return-context given there is no output schema, but the faal's interpretive/fortune-telling nature is only hinted at.

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 tight sentences with the primary mode stated first and the parameter variant second; nothing is padded. The phrase 'read with meanings' is slightly awkward but still economical.

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-only tool with no output schema, the description covers the two modes and defers return-format detail to gj_poem. The deferral to a sibling is a minor gap for an agent unfamiliar with that tool's output, but overall it is sufficient to call 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 description coverage is 100%, and the schema already explains random and poet_id (including that 2 is Hafez) with defaults and minimums. The description only echoes the random=True behavior and says nothing about poet_id, so it adds no meaning beyond the schema — baseline 3.

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 action and resource: draw a Hafez faal (a random ghazal of Hafez), or with random=True a random poem. It also scopes the result ('read with meanings') and points at gj_poem for output shape. It stops short of stating how it differs in intent from the sibling gj_poem beyond output equivalence.

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?

It gives a clear parameter-driven branch (default faal vs random=True for any poet), which is usable guidance. However, it never says when an agent should pick this over gj_poem, gj_poem_extras, or gj_find_verse, and offers no exclusions or prerequisites.

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