Skip to main content
Glama

Update ClawCall call settings

update_call_settings
DestructiveIdempotent

Patch reusable voice/personality or inbound-assistant settings in separate calls. Voice applies to all calls; personality applies to legacy and inbound calls only. Reading, changing, or clearing inbound configuration requires Unlimited Reserve Plus and an active reserved number, or a number on the user's own Twilio account connected to ClawCall; entitlement errors explain why the setting is unavailable and include an informational account-access link. Returns an acknowledgement only; call get_call_settings afterward when read access is available.

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": "update_call_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceNoReusable audio voice. Pass null to reset to the default, eric.
inboundNoInbound assistant patch. Reading, changing, or clearing it requires Unlimited Reserve Plus and an active reserved number, or a number on the user's own Twilio account connected to ClawCall. Pass null to clear it.
personalityNoReusable style for legacy and inbound calls; structured calls use assistant_name and ClawCall conduct. Pass null to clear it.
warm_greetingNoSaved loop-in behavior for inbound and outbound calls. True gives a private briefing and asks before connecting (default); false connects immediately on answer without an AI greeting.

Output Schema

NameRequiredDescriptionDefault
updatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The description adds real context beyond the annotations: partial-patch semantics where omission preserves values, entitlement gating with explanatory errors carrying an account-access link, and that the call returns an acknowledgement only. It does not, however, spell out the irreversibility or blast radius of clearing operations that the destructiveHint=true annotation implies, leaving the destructive risk profile under-described.

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?

Four sentences, front-loaded with the verb-and-resource statement, followed by scope, prerequisites, and return behavior in a logical order. Dense but each sentence carries operational meaning; the entitlement sentence is long yet not padded.

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?

For a four-parameter, destructive, partial-update tool with a nested inbound object, the definition covers gating conditions, patch semantics, side effects of null, and return shape. With an output schema present, no further return-value explanation is needed, and nothing an agent needs before calling is missing.

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 description coverage is 100%, so the baseline is 3; the description earns above that by explaining cross-parameter applicability (voice is global, personality is legacy/inbound only, structured calls use assistant_name and ClawCall conduct). That routing information is not derivable from any individual parameter's schema entry.

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 and resource ("Patch reusable voice/personality or inbound-assistant settings") and immediately scopes each field's reach: voice applies to all calls, personality only to legacy and inbound. It also explicitly separates itself from a read path by pointing to get_call_settings, so an agent can distinguish it from the sibling without opening either 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 clear conditions: patch voice/personality or inbound settings "in separate calls," and call get_call_settings afterward when read access is available. It also names entitlement prerequisites (Unlimited Reserve Plus plus an active reserved number, or an owned Twilio number). It stops short of explicit when-not-to-use guidance, such as which sibling handles structured-call configuration.

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.