CallMCP — Phone Call MCP Server

Save Owner Intake Facts

agency_enrollment_owner_save

Idempotent

Lets the client owner replace the intake facts on their own enrollment link. Requires the owner who claimed the link and the session's current revision. Saving clears any earlier owner approval, so the owner must approve again.

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>",
      "facts": "<facts>"
    },
    "name": "agency_enrollment_owner_save"
  }
}

Input Schema

Name	Required	Description
`facts`	Yes	The full replacement intake facts.
`partnerId`	Yes	The agency (partner) workspace ID.
`sessionId`	Yes	The owner's 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

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses a critical behavioral consequence: saving clears any earlier owner approval, forcing the owner to approve again. It also identifies prerequisite ownership and revision context, giving the agent essential state-change awareness for a mutation tool.

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?

The description is three tightly structured sentences: purpose first, requirements second, side effect third. Every sentence contributes useful information without repetition or filler.

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 complex mutation tool with nested facts, annotations, and an output schema, the description covers the essential owner scope, revision requirement, and approval-reset behavior. It does not describe stale-revision failure handling or return behavior, but the output schema and annotations reduce the need for those details.

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 schema already documents partnerId, sessionId, idempotencyKey, expectedRevision, and the full replacement facts object. The description reinforces the revision and replacement semantics but adds limited meaning beyond what the schema already provides.

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 states a specific verb and resource: replacing intake facts on the owner's own enrollment link. It clearly scopes the action to the client owner, but it does not explicitly distinguish this from sibling save tools such as agency_enrollment_save or agency_enrollment_approve_owner.

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 provides clear usage context by requiring the owner who claimed the link and the session's current revision. It also warns that saving clears prior owner approval and requires reapproval, though it does not name alternative tools or explicit when-not-to-use cases.

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.