Skip to main content
Glama

Search poems by words

gj_search
Read-onlyIdempotent

Search classical Persian poems by exact words to retrieve matching couplets, with optional filters by poet or book and paginated results.

Instructions

Full-text search of poems by the words they contain, with the matching couplet.

All words must appear in the poem. Use gj_semantic_search to search by meaning instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "gj_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 10 results per page.
queryYesPersian words as written in the poem, e.g. 'دل من'.
cat_idNoOnly this book or section (cat_id).
poet_idNoOnly this poet (id from gj_poets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 open-world, so the safety profile is carried by structured data. The description adds genuinely useful behavior: AND-semantics across all terms and that a matching couplet is returned. It stops short of disclosure about result ordering/relevance or the 1000-page ceiling, so it adds value but not rich context.

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, zero filler. The matching contract is front-loaded and the disambiguation sentence follows immediately, so the most decision-relevant facts come first.

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?

Four flat parameters all documented in schema, annotations covering safety, and the description supplies the one thing the schema cannot: the AND-matching rule and the shape of the return (matching couplet). No output schema exists, yet return content is only sketched rather than described, which is the one remaining gap.

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%, so query format (Persian words), page size, cat_id and poet_id are all documented in the schema itself, establishing the baseline of 3. The description's 'All words must appear' adds real meaning about how the query parameter is interpreted, but nothing is said about page, cat_id or poet_id beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full-text search of poems by the words they contain') plus the returned unit ('with the matching couplet'), and explicitly names gj_semantic_search as the contrasting sibling. An agent can distinguish this from the other 16 siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives the selecting condition explicitly: 'All words must appear in the poem' defines the AND-matching contract, and 'Use gj_semantic_search to search by meaning instead' names the alternative and the condition that routes to it. Both when-to-use and when-not-to-use are covered.

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