Skip to main content
Glama
Patience-dot-devl

voice-analysis-mcp

render_spectrogram

Render a mel spectrogram to visually inspect audio for issues like hold music, beeps, or dropouts, with time axis in seconds for transcript mapping.

Instructions

Render a mel spectrogram image of a window (max 600s) for visual inspection.

Look at this to spot things metrics miss: hold music, DTMF/beep tones,
hum, dropouts, TTS glitches, where energy concentrates. Time axis is in
absolute seconds so findings map back to transcript timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
channelNo
end_timeNo
start_timeNo
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the max window size and that the time axis is in absolute seconds, but does not mention whether the tool is read-only, auth requirements, or output format. Adequate but not comprehensive.

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 sentences: first states purpose and constraint, second explains usage and time axis. No unnecessary words, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters and no output schema, the description does not specify the output format (e.g., image file, URL), error handling, or details on all parameters. Incomplete for an agent to invoke correctly without additional inference.

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 0%, so the description must compensate. It adds meaning to start_time and end_time by mentioning the window limit and absolute seconds, but does not explain path or channel. Partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it renders a mel spectrogram image for visual inspection of audio windows up to 600 seconds, with a specific verb and resource. It distinguishes from sibling tools like render_waveform by emphasizing the mel spectrogram and use case for spotting anomalies.

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?

The description explicitly tells when to use the tool: to spot issues that metrics miss (hold music, DTMF, hum, etc.). It does not mention when not to use or compare directly with siblings, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Patience-dot-devl/Voice-analysis.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server