Skip to main content
Glama
Sign In
neuroverse

neuroverse

by joshua400
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Transcribe Audio

neuroverse_transcribe
Read-onlyIdempotent

Transcribe audio files to text using Whisper STT. Provide the absolute path to receive the transcription in JSON.

Instructions

Transcribe an audio file to text using Whisper STT.

Args:

  • audio_path (string): Absolute path to the audio file

Returns: JSON with the transcribed text

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": {
      "audio_path": "<audio_path>"
    },
    "name": "neuroverse_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
audio_pathYesAbsolute path to the audio file to transcribe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already indicate safe, read-only behavior. Description adds only that it returns JSON with transcribed text, but lacks details on file size limits, supported audio formats, or any side effects. Minimal extra value beyond annotations.

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 with clear front-loading of purpose, followed by a structured Args/Returns section. Every sentence is essential and no waste.

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?

Despite simple tool (1 param, no output schema), description lacks important details like supported audio formats, file size limits, or potential error cases. Given sibling tools with different purposes, this missing information could hinder correct invocation.

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 100% with 'audio_path' fully described as 'Absolute path to the audio file to transcribe'. Description repeats this in Args section, adding no new semantic information. Baseline score of 3 is appropriate; no extra context or constraints provided.

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?

Description clearly states verb (transcribe), resource (audio file), and specific technology (Whisper STT). No sibling tool appears to offer transcription, so purpose is distinct and unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives or any prerequisites. Among siblings, there is no similar tool, but explicit context about file format support, size limits, or exclusion criteria is missing.

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