Skip to main content
Glama

CallMCP — Phone Call MCP Server

Finish Self-Service Enrollment

agency_enrollment_finish_self_service
Idempotent

Completes a self-service enrollment after the owner has approved the current intake: creates the client business and queues its package installations, which later configure the business's voice agent. Only the owner who started it can finish it. Repeating it returns the recorded result.

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_finish_self_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdYesThe agency (partner) workspace ID.
sessionIdYesThe owner's enrollment session.
idempotencyKeyNoStable key for this request; reuse it when retrying the same request.

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.1/5.0
Behavior4/5

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

Annotations already declare idempotency, non-destructiveness, and open-world behavior, so the bar is lower; the description nonetheless adds real substance by naming the created artifacts (client business, queued package installations) and their downstream effect on the voice agent. It also discloses the ownership/authorization constraint and confirms repeat calls return the recorded result, though it says nothing about failure modes or partial-failure behavior.

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?

Front-loaded with the action and its effects, then the precondition and the retry semantics. The embedded clause about package installations later configuring the voice agent is useful but slightly tangential; otherwise every sentence carries weight.

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 explanation, and the description covers the precondition, authorization, side effects, and idempotent replay. What remains implicit is what happens if approval has not occurred or how long queued installations take, which are secondary for correct selection and invocation.

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%, with partnerId, sessionId, and idempotencyKey all documented in the schema itself. The description's only added meaning is the ownership tie to sessionId ('only the owner who started it'); it adds nothing about partnerId or the idempotency key, 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?

States a specific verb and resource ('Completes a self-service enrollment') and spells out the concrete effects: creates the client business and queues package installations. The prerequisite clause ('after the owner has approved the current intake') also distinguishes it from the start/approve siblings in the catalog.

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?

Gives a clear precondition for calling (owner approval of the current intake) and an access restriction (only the owner who started the session). It does not explicitly name alternative tools such as agency_enrollment_create or agency_enrollment_enroll, so routing against those siblings still requires inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.