Skip to main content
Glama

CallMCP — Phone Call MCP Server

Claim Owner Enrollment Link

agency_enrollment_claim_owner
Idempotent

Links the signed-in client owner to their enrollment link using its token. The user's verified email must match the owner email on the link. It approves nothing.

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

Input Schema

NameRequiredDescriptionDefault
tokenYesThe token from the owner link.
partnerIdYesThe agency (partner) workspace ID.
sessionIdYesThe owner's enrollment session from the link.
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.2/5.0
Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false), idempotency, and non-destructiveness, so the description doesn't need to repeat those. It does add real behavioral context the annotations lack: the email-match authorization precondition and the explicit negative scope ('approves nothing'), which prevents an agent from expecting approval side effects. It omits what happens on mismatch, a minor gap.

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 short sentences, front-loaded with purpose, then the precondition, then the scope boundary. Every sentence carries distinct information; nothing is repeated from the title or annotations.

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?

With an output schema and annotations covering safety and idempotency, the description supplies the remaining essentials: the linking action, the email-match authorization rule, and the boundary against approval. Only the mismatch/error behavior is left implicit, which is a small gap for a 4-parameter mutation.

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 each parameter is already documented, giving a baseline of 3. The description only adds that the token comes from the owner link; it adds no meaning for partnerId, sessionId, or idempotencyKey beyond what the schema states.

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 ('Links') and resource ('signed-in client owner to their enrollment link'), plus the mechanism ('using its token'). The closing line 'It approves nothing' explicitly demarcates it from agency_enrollment_approve_owner, so an agent can distinguish it from siblings without opening schemas.

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?

Implies the trigger context (an owner following an enrollment link) and gives the eligibility condition: the verified email must match the owner email. It stops short of naming an alternative tool or describing the failure path when the emails don't match, which keeps it below a 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.