KaiCalls

Update Agent Configuration

update_agent_config

DestructiveIdempotent

Edit an agent's live runtime configuration — greeting/first message, inbound or SMS prompt, voice, language model, max call duration, and call-transfer settings — routed through the governed update broker so every change keeps the consent + audit trail (a versioned config snapshot and change history). Every write here is reversible: inspect what changed with get_change_history or list_config_versions, then undo it with rollback_config. Mutating changes need an idempotency_key; high-impact live changes need human authority (an authority envelope) or queue_for_approval for dashboard sign-off. For just a single named operational-rules section, prefer configure_agent_business_rules.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Agent display name.
`actor`	No	Who is asking: { type: agent\|human\|system\|integration, id, display_name }.
`model`	No	Language model selection: { provider, model, temperature }.
`voice`	No	Voice selection: { provider, voiceId }.
`dry_run`	No	Validate and summarize the change without writing.
`agent_id`	Yes	KaiCalls agent ID to update.
`authority`	No	Attribution only. Caller-supplied authority cannot authorize live changes; authenticated owner review of the stored request is required.
`sms_prompt`	No	SMS reply prompt.
`source_ref`	No	External source reference, such as a support ticket or conversation ID.
`business_id`	No	Business ID. Required when the agent has multiple accessible assignments.
`max_duration`	No	Maximum call duration in seconds.
`first_message`	No	Spoken greeting / first message callers hear.
`inbound_prompt`	No	Full inbound system prompt that drives the agent.
`idempotency_key`	No	Required for writes. Reuse the same key when retrying the same change.
`outbound_prompt`	No	Outbound (campaign) system prompt.
`transfer_enabled`	No	Enable/disable live call transfer.
`queue_for_approval`	No	When authority is missing, create a pending dashboard approval instead of returning needs_approval.
`transfer_phone_number`	No	Number to transfer qualified calls to.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No
`error`	No	Present when success is false
`result`	No
`status`	No
`message`	No
`success`	Yes	Whether the tool completed successfully
`summary`	No
`agent_id`	No
`approval`	No
`request_id`	No
`risk_level`	No
`business_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / authority / description

Previous value: -"Human-grade authority for live changes: { mode: human_confirmed|dashboard_session|system_policy, confirmed_by, confirmed_at, confirmation_ref }."New value: +"Attribution only. Caller-supplied authority cannot authorize live changes; authenticated owner review of the stored request is required."

AddedJun 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond what the annotations state, the description discloses the governed update broker, consent and audit trail, versioned snapshots, change history, reversibility via rollback_config, and idempotency/approval requirements. This is substantial behavioral context that would be important for correct and safe invocation.

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?

The description is dense but highly organized: purpose first, then auditability and reversibility, then mutation requirements, then sibling routing. Each sentence earns its place and no content is duplicated or wasted.

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 high-impact mutation tool with 18 parameters, the description covers the operational context an agent needs: governance, audit trail, idempotency, approval flows, reversibility, and alternatives. The presence of an output schema means not explaining return shape is an acceptable shortcut.

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 description doesn't need to restate per-field details. It does add meaningful grouping and behavioral context around important parameters like idempotency_key, authority, and queue_for_approval, lifting it above baseline without making it a full parameter-by-parameter reference.

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 names a specific action and resource: editing an agent's live runtime configuration. It enumerates the field categories clearly, including greeting, prompts, voice, model, max call duration, and transfer settings, and explicitly distinguishes this from configure_agent_business_rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives actionable when-to-use guidance: mutating changes need idempotency_key, high-impact changes need authority or queue_for_approval, and single operational-rules edits should go to configure_agent_business_rules. It also points the agent to rollback_config, get_change_history, and list_config_versions for the associated workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All KaiCalls tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.