CallMCP — Phone Call MCP Server

Start Self-Service Enrollment

agency_enrollment_start_self_service

Idempotent

Starts a business owner's own enrollment in a published agency offer, using the business name and intake facts. Requires a signed-in user session with a verified email and an idempotency key; the same key replays the same session. Nothing is installed until the owner approves and finishes.

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": {
      "offerVersionId": "<offerVersionId>",
      "name": "<name>",
      "facts": "<facts>"
    },
    "name": "agency_enrollment_start_self_service"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The business name.
`facts`	Yes	Intake facts: business profile, hours, qualification questions, routing, fallback, booking, FAQs and reporting.
`idempotencyKey`	No	Stable key for this request; reuse it when retrying the same request.
`offerVersionId`	Yes	The published offer version to enroll 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/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real substance: the replay semantics of the idempotency key ('the same key replays the same session'), the verified-email session requirement, and the key reassurance that no installation occurs until owner approval. It does not cover failure modes such as an unpublished or stale offer version, which keeps it below a 5.

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: purpose first, then requirements and idempotency semantics, then the lifecycle caveat. Every sentence carries distinct information and nothing is repeated from the title.

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?

For a mutation tool with a deep nested intake schema, annotations, and an output schema, the description covers the essentials an agent needs: auth prerequisite, idempotency behavior, and the non-destructive-until-approval guarantee. The only gap is what happens with invalid or unpublished offer versions, a minor omission given the output schema handles returns.

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% and the nested facts object carries its own description, so the schema does the heavy lifting. The description restates the roles of name, facts, and idempotencyKey at a high level but adds no field-level meaning beyond what is already documented, which is the baseline-3 case.

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 description names a specific verb and resource — starting a business owner's own enrollment in a published agency offer — and the 'self-service' framing plus 'owner approves' lifecycle distinguishes it from agency-driven siblings like agency_enrollment_create or agency_enrollment_enroll. It stops short of naming any sibling explicitly, so the differentiation is inferable 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?

It establishes clear preconditions for use: a signed-in user session with a verified email and an idempotency key, plus the requirement that the offer be published. It also hints at the lifecycle handoff ('nothing is installed until the owner approves and finishes'), pointing toward the finish step, but it never states when to choose this over the create/enroll alternatives.

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.