Skip to main content
Glama

Poetic meters

gj_meters
Read-onlyIdempotent

Lists Persian poetic meters with couplet counts, ordered by count, and filters by name so you can identify a meter for similarity search.

Instructions

List poetic meters (وزن) with couplet counts, biggest first; filter by name. Feed a name or id to gj_similar.

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

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a meter name, e.g. 'رمل' or 'هزج مسدس'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely new behavior by disclosing default ordering ('biggest first') and that each result carries a couplet count. It does not say whether the full meter list is returned or truncated, which is the one behavioral gap for an open-world listing.

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 compact clauses separated by a semicolon, verb-first, with the ordering and chaining hint packed in and no filler. Every fragment carries information an agent can act on.

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 one-optional-parameter listing tool with no output schema and adequate annotations, the description covers what is returned, how it is ordered, and how to use the result next. Only the absence of any statement about result size or truncation keeps it from being complete.

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 the single optional parameter already documents itself with worked Arabic examples ('رمل', 'هزج مسدس'). The description only restates 'filter by name' and hints that records carry ids usable by gj_similar, so it adds marginal meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('List poetic meters (وزن)') and adds scope details: couplet counts included, sorted biggest first, optional name filter. An agent immediately knows this is a reference listing, not a search or lookup of a single item. It stops short of naming a sibling it is the alternative to (e.g. gj_literary), so it is clear but not fully differentiated.

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?

'Filter by name' tells the agent the query param is optional narrowing, and 'Feed a name or id to gj_similar' gives explicit downstream chaining guidance. There is no statement of when not to use it or which sibling to prefer for related prosody data, but the usage context is otherwise unambiguous.

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