Skip to main content
Glama

People and characters

gj_people
Read-onlyIdempotent

Search characters from Persian epic poems like Shahnameh by name or alias, view relations and family trees, or list a book's main cast.

Instructions

Look up people and characters of epic poems (Shahnameh...): search, relations, family tree, or a book's cast.

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

Input Schema

NameRequiredDescriptionDefault
idNoPerson id from a search.
viewNoFor id: info, relations (kin and ties with evidence), familytree.info
queryNoSearch characters by name or alias (e.g. 'رستم').
cat_idNoInstead: the main characters and links of a book (e.g. 33).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 openWorld, so safety is covered. The description adds 'relations ... with evidence' for one mode, but says nothing about result size, what happens when no parameters are supplied, or data-source limits for an open-world lookup.

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?

One front-loaded sentence enumerating the four capabilities — efficient, with only minor noise from the parenthetical '(Shahnameh...)' and ellipsis. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All four parameters are optional and there is no output schema, so the definition should clarify default behavior when no arguments are supplied and roughly what each mode returns. It covers the mode vocabulary but not those edge conditions, leaving a moderate gap for a multi-mode lookup tool.

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%, with each parameter documented and an example given for the query. The description's role listing ('search, relations, family tree, or a book's cast') loosely maps to query/view/cat_id but adds no syntax, format, or precedence rules beyond what the schema already states.

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 verb ('look up') and resource ('people and characters of epic poems'), and enumerates the four access modes (search, relations, family tree, book's cast) that correspond to the schema's query/view/cat_id. It does not explicitly contrast with the poet-oriented sibling gj_poet, but the domain is narrow enough to be distinguishable.

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 listed modes imply when to use each (search by name vs. id+view vs. cat_id), but the guidance is only implicit — nothing states prerequisites, such as that an id must first come from a search, or when to prefer gj_poet or gj_book over this tool. Adequate but leaves the agent to infer the routing.

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