Skip to main content
Glama

Recitations

gj_recitations
Read-onlyIdempotent

Fetch poem recitations by exactly one of poem ID, category ID, or latest, returning reciter, MP3 link, file size, and votes; optionally add verse start timings for the best poem recitation.

Instructions

List poem recitations (خوانش) with reciter, mp3 link, size and votes; give exactly one of poem_id, cat_id, latest.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax recitations for cat_id and latest.
cat_idNoTop recitation of each poem in this book/category.
latestNoNewest published recitations site-wide.
poem_idNoRecitations of this poem, best first.
with_timingNoWith poem_id: add start milliseconds of each verse of the best recitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the mutually-exclusive mode constraint and what fields come back, but says nothing about pagination, result ordering beyond the schema's "best first," or rate limits.

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 tight sentence, front-loaded with purpose and followed by the mode rule, with no filler. The extreme density (semicolon-joined clauses, no mention of the limit's role) borders on under-specification rather than ideal structure.

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?

Covers what is returned and the mutual-exclusion rule, which is what an agent most needs for a five-parameter read tool with no output schema. However, since required=[] and every parameter defaults to null/false, the description's "exactly one" requirement is the only signal of behavior and it never states what happens if none is supplied.

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 description coverage is 100%, so the schema already explains each parameter's meaning, making 3 the baseline. The description adds a genuine semantic constraint the schema cannot express: exactly one of poem_id, cat_id, latest must be supplied, despite none being marked required.

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 poem recitations") plus the payload fields returned (reciter, mp3 link, size, votes), which distinguishes it from sibling poets/poems/search tools. It does not explicitly contrast itself with any named sibling, so it stops short of a 5.

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?

Gives an explicit selection rule for the three query modes: "give exactly one of poem_id, cat_id, latest." That is real when-to-use guidance for the ambiguous part of the call, but there are no when-not conditions and no pointer to an alternative tool for adjacent needs.

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