Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Get WhatsApp Status

get_whatsapp_status
Read-onlyIdempotent

Check whether WhatsApp is connected on a business's KaiCalls number, read live from the carrier. Connected only once the number is verified for WhatsApp; otherwise says whether the owner's link is still waiting, expired or failed.

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": {
      "business_id": "<business_id>"
    },
    "name": "get_whatsapp_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
successYesWhether the tool completed successfully
connectedNo
connectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: the value is read live from the carrier, and connected is only true once the number is verified, with distinct waiting/expired/failed states otherwise. That explains what the returned state means and why it may lag, which annotations (readOnly/idempotent) do not cover.

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?

Two compact sentences, front-loaded with the action and resource, with no filler. The second sentence is dense but every clause (verification gate, waiting/expired/failed) carries semantic weight.

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?

Given an output schema exists and annotations already declare the safe read-only profile, the description covers the remaining essentials: what is checked, where the data comes from, and the possible states. Only the identification of business_id is left unstated.

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?

Single parameter with 0% schema description coverage, so the description must carry it. It only implies that business_id scopes the check to a business and its KaiCalls number; it adds no format, source, or error-condition guidance for that identifier.

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?

States a concrete verb and resource: checks whether WhatsApp is connected on a business's KaiCalls number. The scope ('on a business's KaiCalls number') is specific enough to separate it from a generic channel-status check, though no sibling is named for contrast.

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?

Usage is only implied by the object of the check; there is no explicit 'use this when...' or pointer to connect_whatsapp for initiating a link versus this tool for verifying one. An agent can infer the read/verify role, but must decide on its own between this and nearby status siblings.

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

All CallMCP — Phone Call MCP Server 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