Skip to main content
Glama

Place call and wait briefly

place_call_and_wait
Destructive

Place one outbound US call from a structured request and wait up to max_wait_seconds (default 45, max 90) for completion. Suited to a single call, not parallel campaigns. If the call is still running when the wait ends, call track_call with the returned call_id until the event is ended. get_calling_guide topic outbound documents the request fields. The user may see a live card for the 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": {
      "to": "<to>",
      "recipient": "<recipient>",
      "on_behalf_of": "<on_behalf_of>",
      "goal": "<goal>",
      "authority": "<authority>"
    },
    "name": "place_call_and_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesUS E.164 destination such as +14155550123. Look up official public business numbers; ask the user for private details or when listings conflict.
goalYesThe result wanted from this call. Include the full context needed to understand the outcome.
factsNoReference details the recipient may need for this goal, such as account or order numbers, dates, preferences, callback numbers, known menu paths, and prior-call outcomes. The phone agent knows only what the request contains.
voiceNoAudio voice: eric (default), jessica, sarah, or chris. Omission uses the saved voice.
handoffNoPresence enables loop-in. The assistant rings the account's loop-in contacts, or its verified phone when none are set. Include it on most calls. List every situation only the user can handle in handoff.when: one-time codes, account-holder-only policies, identity questions, payments, and decisions outside the authority. The assistant also loops in when the other side asks for the user or a real person.
languageNoLanguage to speak, when you know the recipient prefers one other than English. Speech recognition is tuned for it and English; the assistant can follow the other side into another listed language, less reliably. Omit for English. One of ar (Arabic), bn (Bengali), de (German), en (English), es (Spanish), fr (French), he (Hebrew), hi (Hindi), id (Indonesian), it (Italian), ja (Japanese), kn (Kannada), ko (Korean), mr (Marathi), ms (Malay), nl (Dutch), pl (Polish), pt (Portuguese), ta (Tamil), te (Telugu), th (Thai), tl (Tagalog), tr (Turkish), vi (Vietnamese), zh (Mandarin Chinese).
authorityYesCommitments the assistant may make and their limits. An empty allow list means ask and relay only.
questionsNoQuestions to ask the recipient, including alternatives and follow-up details. Anything the recipient must tell the user, such as a confirmation number or price, belongs here.
recipientYesBusiness, department, or person you expect to reach, including the location.
voicemailNoMailbox outcome: end (default) ends the call without leaving a message; leave_message carries only the words to convey, including authorized callback details. The agent leaves this message on the voicemail, so write it as the message itself, with exact names, numbers, and dates. Put no instructions to the agent inside message.
on_behalf_ofYesPerson or organization the assistant represents. This identifies the requester; it grants no account access.
assistant_nameNoA plain assistant name, such as Jordan. Without it, the agent uses a default name, usually Alex.
max_wait_secondsNoSeconds to wait for finalization, from 5 to 90; default 45. If the call is still running, call track_call.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's job is additive context. It delivers that by disclosing that the tool is only partially synchronous (it may return while the call is still in progress) and that the user may see a live card. It does not mention cost or irreversibility of a real outbound call, though annotations carry the write/open-world signal.

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?

Five short sentences, front-loaded with what it does and the wait bound, followed by the exclusion, the follow-up path, the documentation pointer, and the user-visible side effect. Nothing is redundant with the schema beyond a brief restatement of the wait bound.

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?

For a 13-parameter, nested-object, open-world mutation with an output schema, the definition covers the essentials: scope, wait limit, partial-completion behavior, follow-up tool, and where the request-field documentation lives. Return values need not be described because an output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real value beyond the schema by naming get_calling_guide topic outbound as the authoritative explanation of the request fields, and by restating the wait semantics and the track_call handoff for max_wait_seconds.

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 states a specific verb (place) and resource (one outbound US call) plus scope (single call, not parallel campaigns), so an agent knows exactly what happens. It does not, however, differentiate itself from the closely named siblings place_call and place_call_and_track, which is the highest-risk confusion for a call-placing tool.

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

Usage Guidelines4/5

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

It gives explicit when-to-use ('Suited to a single call, not parallel campaigns') and a clear follow-up path: if still running at the wait deadline, call track_call with the returned call_id. It also points to get_calling_guide topic outbound for request fields. The gap is the absence of a direct comparison to place_call / place_call_and_track.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.