Skip to main content
Glama
Sign In

CallMCP — Phone Call MCP Server

by ai.callmcp
OverviewDiscussionsAdmin

Preview Staff Handoff

agency_installation_preview_handoff
Read-onlyIdempotent

Returns the staff handoff for an installation with a fingerprint for approval. Requires client membership or agency assignment to the client. 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_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 "It changes nothing" mostly restates structured data. The description does add value annotations don't cover: the authorization requirement (client membership or agency assignment) and the fact that the returned fingerprint is intended for a subsequent approval.

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?

Three short, front-loaded sentences with the return value first, then the precondition, then the safety statement. "It changes nothing" is slightly redundant with readOnlyHint but serves as useful emphasis rather than filler.

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-structure explanation is unnecessary; the description still covers what the call yields, the access requirement, and the no-side-effects guarantee. Against a simple four-parameter read tool, nothing material is left for the agent to guess.

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 75% and three of four parameters are documented, including the optimistic-concurrency semantics of expectedRevision. The undocumented fingerprint parameter is only obliquely addressed — the description mentions a fingerprint "for approval" but doesn't clarify whether it is supplied or returned, so it does not fully close that gap.

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?

"Returns the staff handoff for an installation" names a specific verb and resource, and the phrase "with a fingerprint for approval" signals the preview-then-approve relationship. It never names agency_installation_approve_handoff explicitly, so the sibling boundary is inferred rather than stated.

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?

"Requires client membership or agency assignment to the client" gives a concrete precondition an agent can check before calling, and "for approval" implies this precedes an approve step. What is missing is an explicit statement of when NOT to use it or a direct pointer to the approve counterpart.

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