CallMCP — Phone Call MCP Server

Create Client Enrollment Batch

agency_enrollment_create

Idempotent

Creates an enrollment session for 1-50 existing or new clients against a published offer version and returns one owner approval link per new client. Requires an agency owner, admin or operator with access to each existing client, and an idempotency key; a replay returns the session without the links. It sends no email and 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>",
      "offerVersionId": "<offerVersionId>",
      "entries": "<entries>"
    },
    "name": "agency_enrollment_create"
  }
}

Input Schema

Name	Required	Description
`entries`	Yes	One entry per client: either businessId (existing client) or newClient (name, externalRef, ownerEmail), plus expectedRevision and intake facts.
`partnerId`	Yes	The agency (partner) workspace ID.
`ownerEmail`	No	Optional default owner email.
`idempotencyKey`	No	Stable key for this request; reuse it when retrying the same request.
`offerVersionId`	Yes	The published offer version to enroll clients in.

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

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the return payload (one owner approval link per new client), the authorization role required, the idempotency/replay behavior, and two explicit non-side-effects: no email is sent and nothing is installed. That is exactly the kind of context annotations cannot convey.

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?

Three sentences, each carrying a distinct load: what it creates and returns, what it requires, and what it deliberately does not do. No filler and no restatement of the title.

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?

For a batch mutation with a heavy nested schema and an output schema, the description covers the remaining gaps an agent needs: caller authorization, idempotency/replay behavior, batch size limits, and absence of email or install side effects. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning by bounding the entries array at 1-50 and clarifying that a single entry is either an existing businessId or a newClient record, and by reinforcing that offerVersionId must be a published version and the idempotency key stable across retries.

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?

The first sentence states a specific verb and resource ("Creates an enrollment session") and pins the scope precisely: 1-50 clients, existing or new, against a published offer version. It does not name a sibling it is not, so an agent must infer how it differs from agency_enrollment_enroll or agency_enrollment_start_self_service, which keeps it just short of a 5.

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?

Prerequisites are explicit: an agency owner, admin or operator with access to each existing client, plus a mandatory idempotency key. Retry semantics are also given (a replay returns the session without the links). What is missing is any exclusion or routing guidance against the several sibling enrollment tools.

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.