CallMCP — Phone Call MCP Server

Set Call Disclosures

set_call_disclosures

DestructiveIdempotent

Change the recording notice or AI notice callers hear before the greeting, or when each plays. The next call uses the new wording. Requires the business owner. Turning a notice to never can break recording or AI-disclosure law for callers in states that require one; state_gated is the safe default. Every change is logged with the previous value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_call_disclosures"
  }
}

Input Schema

Name	Required	Description
`dry_run`	No	Validate and show the proposed settings without writing.
`business_id`	No	Business ID (optional only when the token has exactly one accessible business)
`ai_disclosure_mode`	No	When the AI notice plays.
`ai_disclosure_enabled`	No	Legacy switch; false turns the AI notice off entirely.
`ai_disclosure_message`	No	What callers hear about talking to an AI. Up to 300 characters.
`record_calls_by_default`	No	Whether calls are recorded. With recording off, no recording notice plays.
`recording_disclosure_mode`	No	When the recording notice plays.
`recording_disclosure_message`	No	What callers hear about recording, e.g. "This call is recorded." Up to 300 characters.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`dry_run`	No
`success`	Yes	Whether the tool completed successfully
`previous`	No
`settings`	No
`business_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the auth requirement, the effect timing ('The next call uses the new wording'), audit behavior ('Every change is logged with the previous value'), and a concrete legal risk for the destructive setting. That is exactly the context the destructive hint alone cannot convey.

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?

Four short sentences, front-loaded with what changes and when it takes effect, followed by prerequisite, risk, and audit note. No filler or repeated schema content.

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

Completeness5/5

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

Covers what changes, when it takes effect, who can call it, the legal risk of the destructive option, and audit logging; an output schema exists, so return values need no explanation. Nothing material is missing for a mutation tool of this complexity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real decision value by recommending state_gated over never for the mode enums and explaining that the notice plays 'before the greeting'. It does not cover dry_run or the legacy ai_disclosure_enabled switch, which remain schema-only.

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 ('Change') plus the exact resources (recording notice, AI notice), including the timing semantics 'before the greeting, or when each plays'. The read counterpart get_call_disclosures is clearly the opposite operation, so an agent can route between them without opening a schema.

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 hard prerequisite ('Requires the business owner'), names an explicit safe default ('state_gated'), and warns about the dangerous setting ('never' can break recording/AI-disclosure law). It does not explicitly point at get_call_disclosures for reading current values, but the operational context is otherwise clear.

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.