CallMCP — Phone Call MCP Server

Save Client Enrollment Batch

agency_enrollment_save

DestructiveIdempotent

Replaces the client entries of an uncommitted enrollment session. Requires the session creator (or an agency owner/admin) and the current session revision. Saving revokes all outstanding owner approval links for the batch, so owners must be sent new links.

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>",
      "expectedRevision": "<expectedRevision>",
      "entries": "<entries>"
    },
    "name": "agency_enrollment_save"
  }
}

Input Schema

Name	Required	Description
`entries`	Yes	The full replacement list of client entries.
`partnerId`	Yes	The agency (partner) workspace ID.
`sessionId`	Yes	The enrollment session.
`idempotencyKey`	No	Stable key for this request; reuse it when retrying the same request.
`expectedRevision`	Yes	The session revision you last read.

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

Behavior4/5

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

Goes well beyond the annotations (destructive=true, idempotent=true) by naming the concrete side effect: all outstanding owner approval links for the batch are revoked and owners must be re-sent links. It also discloses the authorization rule (session creator or agency owner/admin) and the revision precondition. What's missing is any statement about what happens to entries omitted from the replacement list or what a revision mismatch returns.

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 tight sentences, zero filler, ordered from action to authorization to the destructive consequence. The most consequential fact (link revocation) is surfaced rather than buried.

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 destructive batch-replace tool with an output schema and fully described parameters, the description covers the essentials an agent needs to call it safely: replacement semantics, auth requirement, revision precondition, and link-revocation fallout. Return values need no explanation because an output schema exists.

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 baseline is 3. The description reinforces that expectedRevision means the revision last read, but that is already in the schema, and it says nothing about the per-entry expectedRevision, idempotencyKey reuse, or which nested fact buckets are mandatory for a first save.

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?

Opens with a specific verb+resource pair ('Replaces the client entries of an uncommitted enrollment session'), which is far more precise than the name alone. It doesn't contrast itself with the closest siblings (agency_enrollment_owner_save, agency_enrollment_create), so an agent must infer which save path applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Preconditions are stated: the session must be uncommitted, the caller must be the session creator or an agency owner/admin, and the current revision is required. There is no explicit when-not guidance or named alternative for the owner-side save or the create/enroll siblings, so routing is only implied.

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.