CallMCP — Phone Call MCP Server

Retry Activation Notification

retry_activation_notification

DestructiveIdempotent

APPROVAL-GATED. Send the owner's activation notification again, as a real text or email through KaiCalls' messaging provider, for the exact active activation session. Only retries a channel whose last attempt failed or has waited long enough; an attempt whose outcome is unknown is never blindly resent. Requires a new idempotency_key.

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": {
      "business_id": "<business_id>",
      "activation_session_id": "<activation_session_id>",
      "channel": "<channel>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "retry_activation_notification"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes
`authority`	No
`business_id`	Yes
`idempotency_key`	Yes
`activation_session_id`	Yes

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`status`	No
`attempt`	No
`success`	Yes	Whether the tool completed successfully
`business_id`	No
`activation_session_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing that this performs a real external text/email through a provider, that it is approval-gated, and that unknown-outcome attempts are never blindly resent. The annotations already cover destructive/openWorld/idempotent, so the added safety semantics are the valuable part; what is missing is what happens when approval is denied or when the retry is refused.

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 'APPROVAL-GATED' marker, then scope, then safety condition, then the key requirement — no filler sentences. Dense but readable, with each sentence carrying distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the annotations cover the risk profile. However, the unexplained 'authority' and 'business_id' parameters and the absence of any statement about failure/refusal behavior leave real holes for a destructive, externally-facing mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, but it explains only idempotency_key ('must be new') and loosely ties channel and activation_session_id to the described scope. The nested 'authority' object and business_id get no explanation at all, leaving a large gap for a 5-parameter tool.

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 ('Send the owner's activation notification again') with explicit scope: the exact active activation session, via KaiCalls' messaging provider. The retry-only framing distinguishes it from the sibling 'confirm_notification_destination' and from an initial send, though no sibling is named to make the boundary explicit.

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 concrete preconditions for use: only for a channel whose last attempt failed or has waited long enough, never for an unknown outcome, and always with a new idempotency_key. It does not point to an alternative tool when the retry is not permitted, so an agent must infer the fallback.

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.