Skip to main content
Glama

speech_to_text

Read-only

Turn audio into timestamped text with optional speaker separation. Transcription: 0.020 USDC; speaker separation: 0.025 USDC per started minute (1–30).

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": {
      "mode": "<mode>",
      "input": "<input>"
    },
    "name": "speech_to_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is largely covered. The description adds genuinely new behavioral context absent from the structured fields: the exact unit prices and the 1-30 started-minute billing window, which tells the agent this call costs money and is metered. It stops short of describing output shape or failure behavior, though the schema handles refusals and over-length files.

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, zero waste: the capability statement comes first and the cost model second, so the agent hits the purpose before the pricing. Pricing is compressed into a single clause with a range rather than a bulleted list.

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 agent needs the description to convey that results are timestamped text with optional speaker turns, which it does. Safety and mutability are carried by annotations and the nested 'input' schema documents billing and limits thoroughly, so the remaining gap is only the unmapped 'stt'/'diarize' enum and expected response structure.

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?

Reported coverage for the two top-level parameters is 0%, and the description never explains the 'mode' enum values or the 'input' wrapper. It does partially compensate by naming the two operations whose prices differ, letting the agent infer which mode costs more, but it adds no syntax or format detail beyond what the nested schema already spells out for duration_minutes, language, and confidence_threshold.

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 transformation (audio into timestamped text) plus an optional capability (speaker separation), which maps onto the schema's 'stt' and 'diarize' modes. It does not explicitly tie 'speaker separation' to the 'diarize' enum value, so an agent must infer that mapping, but the purpose is otherwise unambiguous.

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?

Pricing per mode implicitly tells the agent that speaker separation is an opt-in upgrade with a cost, which is a light form of selection guidance. There is no explicit statement of when to choose diarization over plain transcription, nor any note on prerequisites such as audio accessibility or size limits; usage is only implied.

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.

Resources