Skip to main content
Glama

CallMCP — Phone Call MCP Server

Replace Owner Enrollment Link

agency_enrollment_rotate_owner_link
Destructive

Issues a new owner link for a client in the batch and invalidates the old one, clearing any earlier claim and approval. Requires the session creator (or an agency owner/admin) and the link's current revision. It sends nothing; the returned link is delivered by whoever re-issued it.

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

Input Schema

NameRequiredDescriptionDefault
partnerIdYesThe agency (partner) workspace ID.
sessionIdYesThe owner's enrollment session to re-issue.
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

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes beyond them by specifying exactly what is destroyed: the old link plus any earlier claim and approval. It also discloses the authorization requirement and the concurrency precondition, which annotations cannot express.

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 tight sentences with the mutation and its destructive side effect front-loaded, then preconditions, then the delivery caveat. Every sentence carries information; 'a client in the batch' is the only slightly opaque phrase.

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 destructive, low-fan-out mutation with a full output schema and full schema coverage, the description supplies the essential missing context: what gets invalidated, who may call it, and that the link is not transmitted. Only failure behavior on a stale revision is left implicit.

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 the schema already documents partnerId, sessionId, expectedRevision, and idempotencyKey. The description paraphrases expectedRevision as 'the link's current revision' and nods at the role, but adds no syntax or selection guidance beyond the schema, so 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?

The description opens with a specific verb and resource ('Issues a new owner link for a client') and immediately states the paired effect ('invalidates the old one'), which makes it distinguishable from revoke/approve/claim siblings without naming them. An agent can tell exactly what state change to expect.

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 gives clear preconditions: caller must be the session creator or an agency owner/admin, and must hold the link's current revision. It also clarifies the delivery model ('sends nothing'), which is a real usage decision point. It stops short of explicitly stating when to prefer this over revoke or a fresh create, so not a full 5.

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.