Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Take Kai Out of a Meeting

leave_meeting
DestructiveIdempotent

Have Kai leave a video meeting it is in, or stop trying to join one. Kai drops out of the live call for everyone in it and stops taking notes; this cannot be undone, and joining again takes a new join_meeting request. Notes taken so far are kept and can be read with get_meeting.

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": {
      "id": "<id>"
    },
    "name": "leave_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMeeting id from join_meeting or get_meeting.
business_idNoBusiness ID (required when the token can access several businesses).

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
meetingNo
successYesWhether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag this as destructive, mutating, and idempotent, but the description adds behavior those annotations cannot express: the drop affects every participant in the live call, note-taking stops, the action is irreversible, and prior notes survive and remain retrievable. That is exactly the kind of consequence and side-effect disclosure a mutation tool needs.

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 tight sentences front-load the action and its two modes, then layer consequence and recovery path. Every clause carries information: scope, irreversibility, note retention, and the rejoin route.

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?

With an output schema present, the description needn't describe return values, and it covers the gaps that matter for a destructive, multi-business-scoped action: effect on other participants, irreversibility, and data retention. Nothing an agent needs to call it safely 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 description coverage is 100%, so both parameters (id, business_id) are already documented, including the origin of the id. The description adds no parameter-level detail and never addresses the conditional business_id, so it matches the baseline rather than exceeding it.

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 states a specific verb and resource (Kai leaves a video meeting) and explicitly covers a second mode (abort an in-progress join attempt). It distinguishes itself from join_meeting and get_meeting by naming them and their roles, so an agent can pick the right tool without opening the schema.

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 gives concrete when-to-use conditions (Kai is in a call, or is still trying to join) and names the alternatives: a new join_meeting to rejoin, get_meeting to read retained notes. The preconditions for each follow-up path are stated rather than inferred.

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