Skip to main content
Glama
Sign In
aspa-mcp

aspa-mcp

by octos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Transcrever áudios

aspa_transcribe_audio
Read-only

Transcribe customer audio messages locally in Brazilian Portuguese with Whisper; audio stays on your machine, and setup guidance is returned if the feature is unavailable.

Instructions

Transcribe customer audio messages locally with Whisper (pt-BR). Optional feature: if it is not installed, the error explains how to enable it. Audio never leaves the machine.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
indexNoIndex from aspa_list_conversations.
contactNoContact name (exact or unique case-insensitive part). Used instead of index.
loadMoreTimesNo
messageIndexesNoItem indexes from aspa_read_conversation. Omit for all audio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already give readOnlyHint=true, so the safe-read profile is covered; the description adds genuinely new behavior: processing happens locally, audio never leaves the machine, output language is pt-BR, and a missing install produces an actionable error. Minor tension with openWorldHint=true is not a contradiction, since the model/runtime may still be fetched externally.

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?

Three short, front-loaded sentences with no filler; the key capability leads and the caveats follow. The phrasing of the middle sentence ('Optional feature: if it is not installed...') is slightly awkward but still earns its place by warning about a failure mode.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should say what the caller gets back (transcripts keyed to message indexes, plain text vs. structured) and how omitted messageIndexes behaves in the response, which it does not. It does cover install prerequisites and privacy, so it is adequate but incomplete for a tool whose entire value is its return payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about any of the four parameters: index, contact, messageIndexes and especially loadMoreTimes, which carries no schema description at all. With coverage at 75% rather than above the 80% baseline, the description needed to compensate for that gap and does not.

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 verb and resource ('Transcribe customer audio messages') plus the engine and language ('Whisper (pt-BR)'), which is far more specific than the title 'Transcrever áudios'. It does not explicitly contrast with any sibling, but no sibling tool performs transcription, so ambiguity is low.

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?

Usage is only implied: an agent can infer it should call this when a conversation contains audio messages it needs as text, but the description never states that condition, nor when not to use it (e.g. when messages are already text). The note about the optional feature being disabled is helpful but is about failure behavior, not selection guidance.

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