Skip to main content
Glama
Sign In

whatsmcp

by com.whatsmcp
OverviewDiscussionsAdmin

Get an AI Voice-Agent Call

wa_ai_call_get
Read-only

[Not usable in this workspace: it acts on every number, and not every number's plan includes it — calling it returns a plan_required refusal; wa_get_plan lists each number's plan.] 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
    • changedOutput schema / properties / refusal / properties / account_status / description
      Previous value: -"when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked"New value: +"when the number is not working: its status — starting, not_running, whatsapp_down (telegram_down for a Telegram account), suspended, pairing, unlinked or locked"
  2. 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"
+  ]
+}
  3. 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"
+}
  4. 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"
+]
  5. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and idempotentHint=false, but the description adds substantial context beyond them: the exact refusal mode (plan_required), where to check eligibility (wa_get_plan), the lifecycle status values, the fact that summary/transcript/collected data only appear after the call ends, and that recording_url expires in one hour. The expiry TTL and partial-result behavior are exactly what an agent needs and cannot get from the schema or annotations.

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?

The availability caveat is front-loaded and the payload sentence is dense but single-purpose with no filler. The second sentence is long — a status list, six return fields, and a TTL in one breath — which slightly hurts scanability but wastes no words.

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?

An output schema exists, so return values did not need spelling out, yet naming them (plus the one-hour recording validity) is genuinely useful. Combined with the prerequisite, refusal mode and eligibility pointer, nothing an agent needs to call 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?

Schema coverage is 100% and the single parameter already documents 'from wa_ai_call_start'; the description restates the same origin rather than adding format or validation detail. With the schema doing the work, 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?

States a specific verb and resource (read an AI call started with wa_ai_call_start) and enumerates exactly what comes back: status values, summary, success judgement, collected data, transcript, and recording_url. An agent can distinguish this from wa_ai_list_calls without opening either schema.

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?

The prerequisite is clear (call_ref comes from wa_ai_call_start) and the caveat routes the agent to wa_get_plan for plan discovery. However, it never says when to prefer this over enumerating with wa_ai_list_calls, and the bracketed 'not usable in this workspace' note leaves the agent unsure whether to call it at all versus skipping straight to the sibling.

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

All whatsmcp 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