CallMCP — Phone Call MCP Server

Preview Client Enrollment

agency_enrollment_preview

Idempotent

Checks every client in the batch for missing facts, owner approval and payer conflicts, and returns what enrolling would install, with the fingerprint and approval IDs needed to enroll. Requires an agency owner, admin or operator. It records the preview on the session but installs 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>",
      "sessionId": "<sessionId>"
    },
    "name": "agency_enrollment_preview"
  }
}

Input Schema

Name	Required	Description
`partnerId`	Yes	The agency (partner) workspace ID.
`sessionId`	Yes	The enrollment session to preview.
`idempotencyKey`	No	Stable key for this request; reuse it when retrying the same request.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`receipt`	No
`success`	Yes	Whether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Adds real value beyond annotations by explaining why readOnlyHint is false despite being a preview: it 'records the preview on the session but installs nothing,' clarifying that it persists state but performs no installation. It does not cover failure behavior for payer conflicts or whether a prior preview is overwritten.

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 tight sentences, front-loading the action and results before the authorization prerequisite and the no-install caveat. Every sentence carries information; nothing is padded.

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 no elaboration, and the description still summarizes what comes back. Authorization and the non-destructive preview semantics are covered, though conflict-failure behavior 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?

Schema coverage is 100%, so partnerId, sessionId and idempotencyKey are already documented. The description only implies the session is where the preview is recorded and adds no syntax or format detail beyond the schema, so the 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?

Uses a specific verb and resource: it checks every client in a batch for missing facts, owner approval and payer conflicts, and states the return payload (fingerprint and approval IDs). The clause 'installs nothing' cleanly separates it from the sibling that actually enrolls.

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?

Implies the correct sequencing by stating it returns the fingerprint and approval IDs 'needed to enroll', and gives the access prerequisite (agency owner, admin or operator). It never explicitly says when not to use it or names the follow-up tool, which keeps it short of a 5.

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 tools Inspect

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.