Skip to main content
Glama

Tajik Cyrillic poems

gj_tajik
Read-onlyIdempotent

Search and read classical Persian poems in Tajik Cyrillic transliteration by query or poem ID, with Cyrillic titles and Persian poet names.

Instructions

Search or read poems in Tajik Cyrillic transliteration (titles Cyrillic, poet names Persian).

Give query to search, or poem_id to read one 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_tajik"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 10 results per page.
queryNoSearch words in Tajik Cyrillic, e.g. 'ошиқ'.
poem_idNoOr a poem id, to read it in Cyrillic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 the safety profile is covered. The description's added value is the transliteration detail (Cyrillic titles, Persian poet names), which helps an agent form valid queries. It does not disclose precedence when both parameters are given, nor anything about result payloads beyond the schema's 10-per-page note.

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, front-loaded with the resource and script constraint, then the mode selection rule. Every clause earns its place with no redundant restatement of the tool name.

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 three-parameter, zero-required read-only tool with a fully described schema and no output schema, the definition covers what an agent needs to pick a mode and supply a value. The remaining gap is the both-parameters/neither-parameter case and the shape of a returned poem, which are minor for this complexity.

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%, and each parameter is already documented with meaning and an example. The description restates the query/poem_id duality and adds the useful hint that titles are Cyrillic while poet names are Persian, but that nuance is only lightly connected to parameter usage. Baseline 3 is appropriate when the schema carries the semantic load.

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 states a specific resource (poems) and two concrete operations (search, read) scoped to Tajik Cyrillic transliteration, plus a useful note about titles being Cyrillic while poet names are Persian. It is clear on its own, though it never names or contrasts with siblings such as gj_search or gj_poem, which likely overlap on search/read behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit parameter-to-mode routing rule: pass query to search, pass poem_id to read a single poem. That is clear usage context for both branches. It stops short of when-not guidance (e.g. what happens if both or neither are supplied) and does not point to alternative tools for broader searches.

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