Skip to main content
Glama
Sign In
video-sense

video-sense

by znplusW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

audio_status

Read-only

Check an independent audio task's source preparation, transcript status, text coverage, and processed ranges; optionally wait up to 20 seconds while preparation or transcription is active.

Instructions

Read an independent audio task: id/mediaId, source metadata, requested/effective source range, statuses.source, statuses.transcript, textCoverage and per-track source/processed ranges. status=ready only means source prepared, not ASR/text complete; statuses.visual=not_applicable. No images. waitSeconds 0..20 waits while source preparation or a text task is active. ASR absent/failed, recognized speech and completed no_speech are distinct; not_enabled is not silence. Use transcript_read for actual original text, session_stop to cancel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "audio_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
waitSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses important semantic behavior: status=ready only means source prepared, visual is not_applicable, no images, and ASR absent/failed versus recognized speech versus completed no_speech versus not_enabled are distinct states. It also explains that waitSeconds waits while source preparation or a text task is active.

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 definition is front-loaded with the main purpose and packed with useful status semantics. It is dense and fragmented rather than prose, with field names and abbreviations like ASR used telegraphically, but most wording carries operational value.

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?

With no output schema, the description does substantial work by enumerating returned fields and explaining status distinctions. It is nearly complete for a status-reading tool with two parameters, though the id/mediaId wording remains slightly ambiguous and some status values are not fully defined.

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 carry parameter meaning. It adds useful semantics for waitSeconds by saying it waits while source preparation or a text task is active, but the id parameter is only referenced as 'id/mediaId' without clarifying UUID format or whether it refers to a task or media identifier.

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 states that it reads an audio task and enumerates the relevant status fields (id/mediaId, source metadata, ranges, statuses.source, statuses.transcript, textCoverage). It distinguishes itself from transcript_read and session_stop, though it does not explicitly contrast itself with audio_start or audio_url_start.

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?

It gives explicit alternatives for reading actual text ('Use transcript_read') and cancelling ('session_stop'), which clarifies some when-not-to-use cases. However, it never directly says when to call audio_status after starting an audio task, nor does it explain polling strategy or when to use audio_start instead.

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

Deploy Server

Other Tools