Skip to main content
Glama

Transcribe a voice message

dosai_transcribe_voice
Destructive

Turn one voice message into text and save it in the dialog (the message content becomes "🎤Распознано: …"). Use it for a voice note that came while the bot was off in that dialog: those are deliberately not transcribed on arrival, so the owner pays only for words someone actually reads. Costs the project's balance per call, so transcribe the messages you need, not the whole history. message_id comes from get_messages, where such a message has message_type voice or audio.

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": {
      "project_id": "<project_id>",
      "message_id": "<message_id>"
    },
    "name": "dosai_transcribe_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage id from dosai_get_messages (message_type voice or audio).
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / message_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds why: the original message content is replaced with the '🎤Распознано: …' marker. It also discloses that each call costs the project's balance and that off-hours messages are deliberately not transcribed on arrival. The only omission is what happens if message_id is not a voice or audio message.

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 three sentences, and the action and its side effect are placed first. The cost sentence includes a short justification ('so transcribe the messages you need'), which earns its place by preventing bulk calls. The 'deliberately not transcribed' clause is slightly verbose but carries the key usage distinction.

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?

For a two-parameter mutation tool with no output schema, the description covers the action, the in-place result of the action, the cost model, and where the ID comes from. What it does not cover is the failure behavior when the message is missing or already transcribed, or the return shape, which is minor given the simplicity.

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 100%, so both parameters are already documented. The description adds provenance by repeating that message_id comes from get_messages with message_type voice or audio, but that meaning is already in the schema, so the gain is marginal. There is no added guidance on project_id or on error conditions.

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 gives a specific verb and resource: 'Turn one voice message into text and save it in the dialog', and it states the observable effect, namely that the message content becomes '🎤Распознано: …'. This distinguishes the tool from automatic on-arrival transcription, so an agent knows exactly what the call does without opening the schema.

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?

It gives an explicit condition for use: 'a voice note that came while the bot was off in that dialog', and an explicit constraint against overuse: 'transcribe the messages you need, not the whole history.' It does not name a sibling alternative to use instead, but none obviously applies, and the cost rationale makes the boundary clear.

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