Skip to main content
Glama

Find the poem of a quoted line

gj_find_verse
Read-onlyIdempotent

Identifies which poem and couplet a quoted Persian line comes from and returns the couplet's meaning, while ignoring spelling, diacritic, and punctuation variations.

Instructions

Locate which poem and couplet a quoted line comes from, with the couplet's meaning.

Spelling differences (ye/kaf, ZWNJ, diacritics, punctuation) are ignored.

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": {
      "text": "<text>"
    },
    "name": "gj_find_verse"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesA line or couplet quoted from memory, in Persian.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful behavioral context: spelling differences in ye/kaf, ZWNJ, diacritics, and punctuation are ignored, and the result includes the couplet's meaning.

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?

The description is two short sentences, front-loaded with the core purpose and followed by one useful normalization detail. Every sentence carries relevant information with no wasted wording.

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 simple one-parameter lookup tool with rich annotations and no output schema, the description covers the purpose, the returned content, and spelling tolerance. It could additionally mention no-match or multiple-match behavior, but it is otherwise complete enough to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the single text parameter is already documented as a Persian line or couplet quoted from memory. The description adds meaningful processing semantics by stating that spelling variations and punctuation differences are ignored when matching the input.

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 uses a specific verb and resource: locate which poem and couplet a quoted line comes from, with the couplet's meaning. It is clearly a reverse-lookup tool, but it does not explicitly distinguish itself from search or semantic-search siblings.

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

Usage Guidelines2/5

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

The description implies usage when the user has a line quoted from memory, but it gives no explicit when-to-use guidance or alternatives. It does not say when to prefer this over broader search tools or how to handle lines that are not exact quotations.

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