get_audioNarration links for a lesson by slug: one MP3 URL per language that has a published recording, so the lesson can be listened to, not just read.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The lesson slug (from search_lessons or get_daily). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already signals a safe read operation. The description adds useful behavioral detail: output is limited to published recordings, returns one MP3 URL per language, and serves an audio-listening purpose, which goes beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the core purpose ('Narration links for a lesson by slug') and then efficiently adds the key output constraint. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter, read-only tool with no output schema, the description provides enough context: what is returned, for which languages, and why it matters. The slug source is covered by the schema description, so no critical information is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the only parameter, slug, is already clearly documented as coming from search_lessons or get_daily. The description reinforces that the slug identifies the lesson but does not add meaning beyond the schema's parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (lesson audio narration links) and the key behavior (one MP3 URL per language with a published recording). It distinguishes the tool from text-focused siblings by noting the lesson can be listened to, not just read, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'so the lesson can be listened to, not just read' implies when audio is needed versus reading the lesson, but it does not explicitly state when to use this tool over get_lesson or get_source_text, nor does it provide exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: catalog discovery, lesson search, source search, lesson retrieval, text retrieval, audio retrieval, daily entry, and Q&A. The two search tools are explicitly separated by corpus (site lessons vs classical sources), and ask is distinct from search by returning grounded answers with citations.
Seven tools follow a clean verb_noun snake_case pattern (search_lessons, get_source_text, list_books, etc.). The single tool named 'ask' is a minor deviation from the verb_noun convention, but it is short and understandable.
Eight tools is well-scoped for a Torah learning library. Each tool has a distinct job, and there is no redundant or filler surface.
The surface covers discovery (list_books), searching (search_lessons, search_sources), retrieval (get_lesson, get_source_text, get_audio, get_daily), and synthesis (ask). This is a read-only content domain, so CRUD operations are not expected; no obvious dead ends remain.