Skip to main content
Glama
kolivri-voice-mcp

kolivri-voice-mcp

Official
by kolivritech

kolivri_get_call_status

Read-onlyIdempotent

Retrieve a Kolivri call's status, outcome, transcript, summary, appointment status, and recording URL by call ID to inspect call results.

Instructions

Retrieve structured call status, outcome, transcript, summary, appointment status, and recording URL for a Kolivri call.

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": {
      "callId": "<callId>"
    },
    "name": "kolivri_get_call_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesUnique Kolivri call ID returned by kolivri_place_call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context by enumerating the returned data, which matters because there is no output schema, but it does not cover permissions, missing transcript behavior, or recording URL availability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the operation and the data returned without filler. The field list earns its place because no output schema exists.

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 low-complexity, single-parameter read tool, the description plus annotations and schema give enough context to invoke it correctly. It usefully enumerates return fields in the absence of an output schema, though it does not describe error cases or whether fields like transcript and recording URL may be absent.

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%, and the callId schema already explains that it is the unique Kolivri call ID returned by kolivri_place_call. The description adds no additional parameter constraints, format details, or lookup semantics beyond referring to a Kolivri call.

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?

States a specific verb, 'Retrieve', and a specific resource set: call status, outcome, transcript, summary, appointment status, and recording URL for a Kolivri call. The operation is unambiguous, though the description does not explicitly contrast it with kolivri_place_call or other siblings.

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 gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. Usage is implied by the tool name and by the schema note that callId is returned by kolivri_place_call, but an agent must infer that this is the follow-up retrieval step.

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