Skip to main content
Glama

Voice note narration audio — Atom

Voice note narration audio

voice_note_narration_audio
Read-onlyIdempotent

Submits a voice-note and narration production record (scoping and confirmation declarations, voice declarations, rights and voice-consent declarations, listening-adaptation declarations, chunking declarations, declared segment rows, audio-spec and assembly declarations, delivery and disclosure declarations, red lines) and returns a deterministic VOICE_NOTE_NARRATION_SOUND / VOICE_NOTE_NARRATION_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across seven sections, including computed segment sequence coverage and exact recomputation of the declared total duration from the declared segment durations, with per-check evidence. Audits the declared record only; it synthesizes no audio, records nothing and clones no voice.

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": "voice_note_narration_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceNoVoice evidence.
rightsNoRights evidence.
scopingNoScoping evidence.
assemblyNoAssembly evidence.
chunkingNoChunking evidence.
deliveryNoDelivery evidence.
segmentsNoDeclared segment rows.
red_linesNoRed lines evidence.
adaptationNoAdaptation evidence.
audio_specNoAudio spec evidence.
production_titleNoProduction under review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing the three possible verdicts, the seven-section structure, the computed segment coverage and the duration recomputation, plus the negative statement that no audio is synthesized or voice cloned. It does not say what happens on malformed input, whether the verdict is cached, or how evidence is surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verb and return contract are front-loaded, but the first sentence is a long run-on parenthesis of eleven declaration types that is hard to parse. It is information-dense rather than padded, yet a bulleted or ordered structure would convey the same content far more efficiently.

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 an 11-parameter tool with nested objects and no output schema, the description does carry the return-value burden by naming the verdict enum, the seven sections and per-check evidence. The gap is that the structure of the nested declaration objects is only referenced via an external SERVICE.md, which leaves an agent without the field-level detail needed to build a valid manifest.

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 the baseline is 3. The description groups the parameters into semantic families (scoping/confirmation, voice, rights and consent, adaptation, chunking, segments, audio-spec, assembly, delivery, red lines), which lightly clarifies intent, but it adds no detail about the expected shape of these nested objects and defers the field table to an external SERVICE.md the agent may not have.

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 names a specific action (submits a production record for a voice-note/narration) and the exact output (a deterministic verdict across three enumerated values and seven sections). It is unambiguous about what the tool does, though the dense enumeration of declaration types makes the core purpose slower to extract than it should be.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent must infer that this is the validation step for an already-assembled manifest. The closing line 'Audits the declared record only; it synthesizes no audio, records nothing and clones no voice' is a useful scope exclusion, but there is no explicit when-to-use or when-not-to-use guidance and no alternatives are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.