Skip to main content
Glama
Sign In
Gemini MCP Server

Gemini MCP Server

by salviz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

gemini_analyze_audio

Transcribe, summarize, and describe audio files using Gemini AI for detailed analysis.

Instructions

Analyze an audio file with Gemini (transcribe, summarize, describe)

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": {
      "audioPath": "<audioPath>"
    },
    "name": "gemini_analyze_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel name (default: gemini-3.1-pro-preview)
promptNoPrompt for audio analysis (default: Transcribe and describe this audio)
audioPathYesAbsolute path to the audio file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only lists high-level capabilities (transcribe, summarize, describe) without covering potential side effects, permissions, rate limits, or output format. This is insufficient for an AI agent to understand the tool's full behavior.

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 a single, concise sentence that is front-loaded with the tool's purpose. It is appropriately brief, though could benefit from a structured breakdown of capabilities.

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?

Given no output schema and no annotations, the description should provide details on return values, output format, or processing duration. It lacks completeness for a tool that performs multiple analysis tasks, leaving the agent without critical usage context.

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?

The input schema has 100% description coverage for all three parameters (model, prompt, audioPath). The tool description adds minor context for the prompt parameter by mentioning the default, but does not significantly enhance understanding beyond the schema.

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 clearly states the tool analyzes audio files with Gemini, listing three capabilities (transcribe, summarize, describe). It distinguishes from sibling tools like gemini_analyze_image by specifying audio, but could be more precise about the analysis scope.

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 is provided on when to use this tool versus alternatives like gemini_analyze_video or gemini_analyze_youtube. The description lacks context for preferred use cases or exclusions.

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