Skip to main content
Glama
AgentPhone-AI

AgentPhone MCP Server

Official
by AgentPhone-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

make_conversation_call

Place an AI phone call to conduct an autonomous conversation about a topic such as scheduling, surveys, or follow-ups without webhook setup; returns the full transcript by default.

Instructions

Place a phone call where the AI has an autonomous conversation about a given topic — scheduling, surveys, follow-ups, etc. No webhook setup needed.

The agent must have a phone number attached. Every call automatically opens with an automated-assistant disclosure (added server-side; cannot be disabled via topic or initial_greeting). By default this blocks until the call finishes and returns the full transcript. Set wait=false for fire-and-forget.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoWhen true (default), blocks until the call ends and returns the full transcript.
topicYesThe conversation goal for the assistant to pursue. Embedded as the call objective within locked instructions that always enforce the automated-assistant disclosure (it can't be overridden). Be specific about what to discuss and any goals.
voiceNoVoice ID override for this call
agent_idYesThe agent ID (must have a phone number attached)
to_numberYesRecipient phone number in E.164 format (e.g. +14155551234)
from_number_idNoSpecific phone number ID to call from (if agent has multiple numbers)
initial_greetingNoWhat the AI says when the call connects. If not set, the AI will generate one from the topic.
max_wait_secondsNoMaximum seconds to wait for the call to complete. Defaults to 300 (5 minutes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only carry openWorldHint, so the description does the heavy lifting and does it well: it discloses a server-side, non-disableable automated-assistant disclosure, the default blocking behavior with transcript return, and the wait=false escape hatch. It omits cost, concurrency, and failure/retry behavior, keeping it short of a 5.

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?

Four tight sentences, each carrying distinct information, with the core behavior and the blocking default front-loaded. Nothing is redundant with the schema or wasted.

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?

Covers prerequisites, side effects, blocking semantics, and return behavior (full transcript) for an 8-param tool with no output schema. Minor gaps remain around transcript format and any cost/latency expectations, but an agent has what it needs to invoke correctly.

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 all 8 parameters are documented in the schema, so the baseline is 3. The description reinforces wait semantics and the locked nature of topic but adds no syntax or format detail beyond what the schema already provides.

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 and resource ('Place a phone call') plus the distinguishing capability ('AI has an autonomous conversation about a given topic'), which separates it from the plain make_call sibling without naming it. The scope is clear enough that an agent can pick it over make_call from the description alone.

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?

Gives prerequisites ('The agent must have a phone number attached') and notes 'No webhook setup needed', which is useful context. However, it never explicitly says when to use this versus make_call or send_message, so the routing guidance is only implied.

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