Splitwise MCP Server

voice_command

Transcribes base64 audio using Deepgram, interprets intent with Gemini, and executes Splitwise expense actions from voice commands.

Instructions

Process a voice command for Splitwise.

Accepts base64-encoded audio (WAV or MP3 format), transcribes it using Deepgram, processes the intent using Gemini, and executes Splitwise actions.

Args: audio_base64: Base64-encoded audio data (WAV or MP3).

Returns: The result of the voice command (e.g., confirmation, clarification request, or error).

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_base64": "<audio_base64>"
    },
    "name": "voice_command"
  }
}

Input Schema

Name	Required	Description	Default
`audio_base64`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2May 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the high-level process (transcription, intent, execution) and possible returns (confirmation, clarification, error). However, it does not detail potential side effects like data modification or required permissions.

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 front-loaded with purpose and efficiently explains the process. Minor redundancy (first sentence then restates) but overall well-structured and concise.

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?

Despite complexity (voice pipeline with external services), the description covers the process, input, and return types. Mentions Deepgram and Gemini. Lacks details on audio size limits or latency, but still fairly complete given output schema exists.

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

Parameters4/5

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

The schema has only one parameter (audio_base64) with no description. The description adds meaning by specifying format constraints (WAV or MP3) and encoding. Given 0% schema coverage, the description compensates well.

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 clearly states that the tool processes voice commands for Splitwise by accepting base64 audio, transcribing it, processing intent, and executing actions. It distinguishes itself from siblings like text_command by explicitly focusing on voice input.

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 such as text_command. The description does not mention prerequisites, when voice is appropriate, or when not to use it.

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

Deploy Server