Dialyne

Get call status and result

get_call

Read-onlyIdempotent

Get the status and written result of a call placed with place_phone_call (outcome, summary, pending question, transcript on request), optionally waiting for news. Compliance: read-only; transcripts are text only (no audio is recorded) and are kept 90 days at most.

Use it to follow a call in progress (repeat until done=true), to see whether the voice agent is waiting for the user's answer (pending_question), and to read the final outcome and summary to report to the user. Read-only: it never places, changes or ends a call.

Returns: status (scheduled, in_progress, retry_scheduled, completed, cancelled, failed), done, outcome (success, failed, voicemail, no_answer, busy, callback_requested, callee_objected), summary, pending_question {question_id, text}, new events since after_event_id, last_event_id and next_step. A call that is busy or not answered is retried automatically (status retry_scheduled), except on lines where every call needs a new request from the user (event callback_suggested: ask the user). callee_objected means the person asked not to be called again: the transcript was deleted and the number can no longer be called; tell the user.

Input Schema

Name	Required	Description	Default
`call_id`	Yes	The call_id returned by place_phone_call or list_calls (e.g. 'mis_…').
`wait_seconds`	No	Seconds (0-50) to wait for news before returning: returns early when the callee answers, the call goes on hold, the voice agent asks a question, a transfer progresses or the call ends. Use 20-30 while a call is in progress, 0 for an instant snapshot.
`after_event_id`	No	Return only events after this id: pass last_event_id from the previous get_call response. 0 = from the start.
`response_format`	No	'concise' (default): status, outcome, summary, pending question and key events. 'detailed': also every transcript line, talk and hold durations, attempts and scheduled time.	concise

Output Schema

Name	Required	Description	Default
`done`	No
`events`	No
`status`	No
`call_id`	No
`outcome`	No
`summary`	No
`attempts`	No
`language`	No
`next_step`	No
`transcript`	No
`latest_line`	No
`hold_seconds`	No
`phone_number`	No
`last_event_id`	No
`scheduled_for`	No
`pending_question`	No
`talk_seconds_billed`	No
`new_transcript_lines`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses non-obvious behavior: automatic retry with status retry_scheduled, the exception for lines requiring a new user request, transcript retention of 90 days, text-only transcripts with no audio, and that callee_objected deletes the transcript and blocks the number.

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

Conciseness3/5

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

The when-to-use guidance is front-loaded and valuable, but the Returns paragraph enumerates status, outcome and event fields that the output schema already carries, making the definition longer than necessary without adding proportional value.

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 polling tool, the definition covers the complete loop an agent needs: how to poll, when to stop, how to consume events via last_event_id, how retries surface, and the exceptional terminal states. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so call_id, wait_seconds, after_event_id and response_format are already fully documented with ranges, defaults and examples. The description only adds light context ('optionally waiting for news', 'transcript on request') that maps loosely to wait_seconds and response_format, so baseline 3 applies.

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 opening sentence names a specific verb and resource (get the status and written result of a call) and ties it to the originating tool place_phone_call, making the relationship to siblings like list_calls or place_phone_call unambiguous.

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?

It states concrete usage patterns: poll repeatedly until done=true to follow a call in progress, check pending_question, and read the final outcome. It also sets explicit boundaries ('it never places, changes or ends a call') and explains what to do on event callback_suggested and on callee_objected.

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

All Dialyne tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.