Skip to main content
Glama
sebastienfi

MCP Vapi Caller

by sebastienfi

get_call_result

Fetch the outcome of a phone call started via make_call, including transcript, AI summary, success evaluation, extracted data, and recording URL. Optionally wait for completion.

Instructions

Check the outcome of a call initiated by make_call().

Returns the call status, transcript, AI-generated summary, success evaluation, structured extracted data, and recording URL.

USAGE:

  • For a quick status check: get_call_result(call_id="...")

  • To wait for completion: get_call_result(call_id="...", wait_seconds=180) This polls every 5 seconds until the call ends or the timeout is reached.

TYPICAL CALL DURATION: 1-3 minutes. Use wait_seconds=180 for most calls.

RETURNED FIELDS (when call has ended):

  • call_id: The call identifier

  • status: "ended" when complete

  • ended_reason: Why the call ended (e.g. "assistant-ended", "customer-ended")

  • summary: AI-generated summary of the conversation

  • success: Success evaluation based on the call_goal

  • structured_data: Extracted data matching the schema from make_call (if provided)

  • transcript: Full conversation transcript

  • recording: URL to the call recording audio file

If the call is still in progress, returns the current status without the analysis fields. Call again with wait_seconds to poll.

Args: call_id: The call ID returned by make_call wait_seconds: If > 0, poll every 5s up to this duration waiting for the call to end. 0 means check once and return immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYes
wait_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, but the description fully discloses polling behavior, timeout, and the conditional return of fields. It shows exactly what is returned when the call has ended versus in progress, adding rich behavioral context beyond the schema.

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?

The description is well-structured with sections (USAGE, TYPICAL CALL DURATION, RETURNED FIELDS, Args). It is detailed but every sentence contributes, with no redundancy or fluff.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all key aspects: status check, waiting, return fields, polling behavior, and conditional responses. Despite having an output schema, the description adds essential context about the tool's runtime behavior, making it complete for an agent to invoke correctly.

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

Parameters5/5

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

The input schema has no property descriptions (0% coverage), but the description explains both parameters thoroughly: call_id as the ID returned by make_call, and wait_seconds with its polling semantics and default behavior. This compensates fully for the schema gap.

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 opens with 'Check the outcome of a call initiated by make_call()', which is a specific verb+resource statement. It clearly distinguishes from the sibling make_call tool by focusing on result retrieval rather than initiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage patterns: quick status check with call_id only, or waiting via wait_seconds=180 for typical 1-3 minute calls. Explains polling interval (5 seconds) and timeout behavior, plus what to do if the call is still in progress.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienfi/mcp-vapi-generic-caller'

If you have feedback or need assistance with the MCP directory API, please join our Discord server