Skip to main content
Glama

analyze_call

Analyzes a single customer-service call from audio, URL, transcript JSON, or demo ID and saves results locally, returning sentiment, contact reasons, key moments, and a transcript excerpt.

Instructions

Analyze one customer-service call and save the result in the local database.

    source: a local audio file, an http(s) URL to an audio file, a local JSON file of transcript
    segments [{start, end, text}], or a demo call id (demo-1 ... demo-6).
    started_at: ISO date-time of the call (default: now). language: e.g. "fr" or "en" (audio only).
    Returns sentiment, contact reasons, key moments (complaint, churn threat, agent promise) and a
    transcript excerpt. Runs locally: audio is transcribed on this machine.

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": {
      "source": "<source>"
    },
    "name": "analyze_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
call_idNo
languageNo
started_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the write side effect (result is saved to the local database), states that processing runs locally and audio is transcribed on this machine, and names the returned fields. It omits what happens when call_id already exists (overwrite vs new row) and any latency/cost expectations for transcription.

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?

Front-loaded with the action and side effect, then a compact list mapping each input to its semantics, then return values. Slightly list-like and could trim the repeated articles, but every sentence contributes information.

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?

No output schema exists, yet the description summarizes the return payload (sentiment, contact reasons, key moments, transcript excerpt), and the mutation side effect plus local-processing model are stated. The only substantive omission is the role and reuse semantics of call_id.

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 0%, so the description must compensate; it documents three of four parameters in useful detail (source formats, ISO date-time with 'now' default, language as a short code applying only to audio). The fourth parameter, call_id, is never mentioned, leaving a meaningful gap at this coverage level.

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?

States a specific verb and resource ('Analyze one customer-service call and save the result in the local database') plus the scope (one call). This is clearly distinct from siblings like search_feedback or suggest_actions, which operate on aggregated feedback or actions rather than a single call.

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?

The description enumerates acceptable inputs (local audio file, http(s) URL, transcript JSON, demo-1..demo-6), which implicitly tells the agent when this tool applies. However it never names an alternative or states when not to use it, and does not clarify whether re-analyzing an already-analyzed call is expected.

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