Skip to main content
Glama
smallest-inc

Smallest MCP Server

Official
by smallest-inc

update_agent_config

Update an AI agent's configuration including name, language, voice, model, and variables. Only provided fields change; versioned agents save as draft.

Instructions

Update an agent's configuration (name, language, first message, voice settings, model, variables, etc.). Only provided fields are updated. To update the agent's prompt/instructions, use update_agent_prompt instead. For versioned agents, changes are saved as a draft — use publish_draft to make them live, or test the draft first via make_call with the draft's version_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe agent ID to update
nameNoNew agent name
descriptionNoAgent description
languageNoLanguage configuration
first_messageNoFirst message when call starts (max 500 chars)
synthesizerNoVoice synthesizer configuration
slm_modelNoInference LLM model for the agent
global_promptNoGlobal system prompt for the agent (max 4000 chars). This is separate from the workflow prompt updated via update_agent_prompt.
default_variablesNoDefault variables for the agent prompt. Example: { prospect_name: 'Default', company: 'Acme' }
knowledge_base_idNoKnowledge base ID to attach to the agent
allow_inbound_callNoWhether to allow inbound calls
allow_interruptionsNoWhether to allow user interruptions
wait_for_user_to_speak_firstNoWait for user to speak before agent starts
mute_user_until_first_bot_responseNoMute user audio until the bot sends its first response
interruption_backoff_timerNoDelay in seconds before agent resumes after interruption (0-10)
smart_turn_configNoSmart turn detection configuration
voice_detection_configNoVoice activity detection configuration
voicemail_detectionNoVoicemail detection configuration
denoising_configNoAudio denoising configuration
llm_idle_timeout_configNoLLM idle timeout configuration per call type
session_timeout_configNoSession timeout configuration
background_soundNoBackground sound option
speech_formattingNoEnable speech formatting
pronunciation_dictsNoCustom pronunciation dictionary
redaction_configNoRedaction configuration
call_disposition_configNoCall disposition configuration prompt
enable_style_guideNoEnable conversational style guide
telephony_product_idsNoList of telephony product IDs (phone numbers) to assign to this agent
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions partial update behavior and draft handling for versioned agents, but does not disclose authorization requirements, what happens for non-versioned agents, or whether the update is immediate. Some constraints are included (max 500 chars for first_message, max 4000 chars for global_prompt), but more behavioral context would be beneficial.

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 three sentences, front-loaded with the core purpose, then provides key usage guidelines. Every sentence is necessary and contributes to understanding. No wasted words.

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?

Given the complexity (28 parameters, many nested), the description covers update behavior and draft handling but lacks details on non-versioned agents, error scenarios, return values (no output schema), and authentication. The schema descriptions are thorough, so the description is adequate but not fully comprehensive.

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 baseline is 3. The description adds value beyond the schema by stating 'Only provided fields are updated' and highlighting the draft behavior for versioned agents. It also references some constraints from the schema (e.g., max lengths). This adds meaningful context for parameter usage.

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 clearly states 'Update an agent's configuration' and lists the fields. It distinguishes itself from the sibling tool 'update_agent_prompt' by explicitly stating that the latter should be used for prompt/instructions updates.

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 provides explicit guidance: 'Only provided fields are updated.' It also explains the behavior for versioned agents (changes saved as draft, use publish_draft to make live, or test via make_call with draft's version_id). Additionally, it directs to use update_agent_prompt for prompt updates.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smallest-inc/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server