Skip to main content
Glama

Dial by Aloha Labs

get_call_result

Get the result of a call from make_phone_call: status, outcome, summary and transcript. Waits up to wait_seconds for the call to finish; if it's still going, call again.

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": {
      "api_key": "<api_key>",
      "call_id": "<call_id>"
    },
    "name": "get_call_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesYour Dial API key (from sign_up)
call_idYes
wait_secondsNoHow long to wait for the call to end (default 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose the key non-obvious behavior: the call blocks up to wait_seconds (max 120 per schema) and returns partial state while the call is still running rather than failing. It does not cover error cases (unknown call_id) or cost/rate implications, which keeps 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?

Two sentences, front-loaded with the returned fields and followed by the polling instruction. Nothing is repeated from 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?

No output schema exists, and the description compensates by naming the four returned fields; polling behavior and the default/max wait are covered via schema. Only failure-mode behavior (invalid or expired call_id) is left unspecified.

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 67%, and the description compensates for the undocumented call_id by tying it to the call produced by make_phone_call. It also gives intent for wait_seconds (how long it will block), reinforcing the schema's own "default 90" note.

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 ("get the result of a call") and names the originating sibling tool make_phone_call, plus enumerates what comes back (status, outcome, summary, transcript). An agent can instantly separate this polling/retrieval tool from make_phone_call or the phone-number management siblings.

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?

Makes the usage pattern explicit: it is the follow-up to make_phone_call and should be re-invoked if the call is still in progress. No explicit when-not-to-use or pointer to alternatives, but for this tool the invocation condition is fully clear.

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.