Skip to main content
Glama

WhatsMCP: MCP for WhatsApp

by com.whatsmcp.app
OverviewDiscussionsAdmin

Get an AI Voice-Agent Call

wa_ai_call_get
Read-only

Read an AI call started with wa_ai_call_start: status (dialing, in_progress, done, failed, no_answer, busy), and once it has ended the summary, whether the agent judged it successful, the data it collected, the transcript, and a recording_url valid for one hour.

Input Schema

NameRequiredDescriptionDefault
call_refYesfrom wa_ai_call_start

Output Schema

NameRequiredDescriptionDefault
callNothe call; transcript, summary and data fill in once it has ended
nextNowhat to do next
refusalNopresent only when the request was declined
recording_urlNoMP3 of the call, valid for one hour; present once recording_state is saved

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / refusal / properties / candidates
      Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
  2. Changed3 schema fields changed
    • addedOutput schema / properties / refusal / properties / account_status
      Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / account_status_reason
      Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}
    • addedOutput schema / properties / refusal / properties / since
      Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • addedOutput schema / properties / call / properties / direction
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / call / properties / from
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / call / required
      Previous value: -[
-  "call_ref",
-  "status",
-  "preset",
-  "account_id",
-  "to",
-  "created_at",
-  "recording_state"
-]New value: +[
+  "call_ref",
+  "direction",
+  "status",
+  "preset",
+  "account_id",
+  "to",
+  "created_at",
+  "recording_state"
+]
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral detail beyond them: the full status vocabulary, the fact that summary/success/collected-data/transcript only exist once the call has ended, and a one-hour expiry on recording_url. Those are exactly the operational details an agent cannot get from the structured fields.

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

Conciseness4/5

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

One front-loaded sentence: verb and resource first, then the status list, then the post-completion fields. The tail is cumulative and dense, but every clause (status set, post-end availability, URL expiry) carries information an agent needs.

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?

Return shape is backed by an output schema, yet the description still tells the agent which fields are conditional and when the recording link expires. Nothing needed to invoke this 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?

The single call_ref parameter is 100% documented in the schema, and the description only restates its origin ('started with wa_ai_call_start'). With coverage this high the schema is doing the work, 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 description opens with a specific verb+resource ('Read an AI call') and immediately scopes it to calls created by wa_ai_call_start, which cleanly separates it from wa_ai_list_calls and wa_ai_call_hangup. The enumerated status values confirm exactly what kind of object is returned.

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?

'Read an AI call started with wa_ai_call_start' establishes the prerequisite and implies polling, since statuses like dialing/in_progress indicate it is meant to be called before the call ends. It never names a sibling alternative or states an explicit when-not condition, so it falls short of a 5.

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

All WhatsMCP: MCP for WhatsApp toolsInspect
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.

Resources