Skip to main content
Glama

CallMCP — Phone Call MCP Server

Approve Owner Enrollment

agency_enrollment_approve_owner
Idempotent

Records the client owner's approval of the exact offer and intake facts on their enrollment link. Requires the owner who claimed the link, the session's current revision and its fingerprint. It does not enroll; the agency still enrolls the batch.

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>",
      "fingerprint": "<fingerprint>"
    },
    "name": "agency_enrollment_approve_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdYesThe agency (partner) workspace ID.
sessionIdYesThe owner's enrollment session.
fingerprintYesThe session's request fingerprint you reviewed.
idempotencyKeyNoStable key for this request; reuse it when retrying the same request.
expectedRevisionYesThe session revision you last read.

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

A3.9/5.0
Behavior4/5

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

Annotations already flag this as a non-destructive, idempotent write. The description adds context beyond that: it is a consent-recording step tied to a claimed owner session and guarded by the session revision and fingerprint, which signals optimistic-concurrency protection against stale approvals.

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 short sentences that front-load the action and then state prerequisites and scope. No wasted wording, though the prerequisite list could be partitioned slightly more crisply.

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 not be explained, and the description covers the write's prerequisites and its place in the flow. For a mutation tool of this complexity, that is nearly everything an agent needs before invoking it.

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 all five parameters are already documented. The description reinforces that expectedRevision is the session's current revision and fingerprint is the reviewed one, but adds no new format or constraint detail beyond the schema.

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?

States a specific verb and resource: records the client owner's approval of the exact offer and intake facts on an enrollment link. It also draws a functional boundary ('It does not enroll; the agency still enrolls the batch'), which separates it from the enrollment action without naming a sibling tool directly.

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 – the owner must have claimed the link, and the session's current revision and fingerprint are required – and clarifies the follow-on step belongs to a different action. It stops short of naming the specific sibling to call next or an explicit when-not-to-use case.

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.