Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Preview Installation Offboarding

agency_installation_preview_offboard
Read-onlyIdempotent

Shows what offboarding would stop and what it keeps (phone number, sender, connections, billing plan and history), with a fingerprint for approval. Only the client owner can view it. It changes nothing.

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": {
      "partnerId": "<partnerId>",
      "installationId": "<installationId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "agency_installation_preview_offboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
acceptedNo
partnerIdYesThe agency (partner) workspace ID.
fingerprintNo
installationIdYesThe agency package installation to act on.
expectedRevisionYesThe installation revision you last read. The call is rejected if the installation has changed since.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds value by naming the authorization constraint (only the client owner) and enumerating exactly which resources survive offboarding, which directly answers the operator's main question. 'It changes nothing' merely restates the annotations rather than adding new behavior.

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 sentences, front-loaded with the preview outcome and the retained resources, followed by the permission constraint and the no-change guarantee. No filler or redundancy beyond one reinforcing clause.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The definition adequately covers permission, scope and non-mutation, though it leaves the 'accepted' parameter and revision-conflict handling unexplained for a five-parameter tool.

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 60%, with partnerId, installationId and expectedRevision documented in the schema. The description only ties the 'fingerprint for approval' concept to the fingerprint parameter and says nothing about the 'accepted' boolean or the revision-staleness rejection path, so it adds marginal meaning beyond the schema.

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 specific verb and resource ('shows what offboarding would stop and what it keeps') plus the concrete domains affected (phone number, sender, connections, billing). This clearly separates it from the mutation sibling agency_installation_offboard, though it does not name that sibling explicitly.

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?

'with a fingerprint for approval' implies the preview is the prerequisite step in a preview-then-approve-then-offboard workflow, and 'Only the client owner can view it' gives a precondition. It stops short of naming the approve/offboard tools or stating when a preview is unnecessary.

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