Skip to main content
Glama
ykshah1309

live-audio-intelligence-mcp

by ykshah1309

analyze_speaker_stress

Analyze vocal stress in live audio streams to detect nervousness, evasion, and uncertainty, flagging potential market-moving signals such as guidance revisions.

Instructions

Analyse the speaker's vocal stress over a recent time window.

Extracts F0 pitch contour, measures pitch jitter (vocal tremor), and detects hesitation patterns (pauses > 400ms). Returns a composite stress score from 0–100 where:

0–20 = confident, fluent delivery 20–45 = normal variation 45–75 = elevated stress — worth monitoring 75–100 = high stress — potential market-moving signal

Higher scores correlate with executive nervousness, evasion, and uncertainty — the kind of prosodic signals that precede guidance revisions and earnings misses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stream_idYes
time_window_secondsNoAnalysis window in seconds

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stream_idYes
time_window_secondsYes
stress_scoreYesComposite vocal stress score 0-100
pitch_mean_hzYesMean fundamental frequency in Hz
pitch_std_hzYesStandard deviation of F0
pitch_jitterYesNormalised pitch jitter (coefficient of variation)
hesitation_ratioYesFraction of audio that is silence >400ms
voiced_fractionYesFraction of voiced frames
pause_countYesNumber of significant pauses detected
longest_pause_msYesDuration of longest pause in ms
analysisYesHuman-readable stress interpretation
chunks_analyzedYesNumber of audio chunks processed
Behavior4/5

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

With no annotations, the description fully discloses the analysis process (pitch extraction, jitter, hesitation detection) and the meaning of the composite score. However, it does not mention side effects, data persistence, or permissions, but for a read-only analysis this is acceptable.

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?

The description is well-structured and concise, with a clear summary followed by feature list and score interpretation. The final speculative paragraph is slightly verbose but does not detract significantly.

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?

The output schema exists, so the description does not need to detail return format. It provides score ranges and feature explanation. Prerequisites (e.g., active stream) and error conditions are not mentioned, but overall sufficient for typical usage.

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 50% (only time_window_seconds has a description). The description adds context about the time window and pause threshold but does not explain stream_id beyond its necessity. Overall, moderate value added beyond schema.

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 the tool analyzes speaker vocal stress over a recent time window, details extracted features (F0 contour, jitter, hesitation patterns), and provides a composite stress score. This differentiates it from sibling tools which handle transcription or monitoring.

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?

The description implies usage for analyzing stress in a recent window of a live stream but lacks explicit guidance on when to use this tool versus siblings or prerequisites like stream activity. Score ranges provide context but no direct usage direction.

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/ykshah1309/live-audio-intelligence-mcp'

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