Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

updateAgent

Modify an existing voice agent's configuration by sending only the fields you want to change. Update model, voice, transcriber, transfer, call-end behavior, and more.

Instructions

Update an existing agent. Send only the fields you want to change.

Voicemail detection is an access-gated feature that we turn on per account. If it isn't enabled for yours yet, request access before configuring the voicemail object below. (Tags: Agents)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe ID of the agent.
requestBodyYesAgent configuration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / requestBody / properties / timezone
      Added value: +{
+  "description": "IANA timezone for this agent, for example `Asia/Kolkata`. Sets the local date and time the agent works with during calls. If not set, the account timezone is used as fallback. Pass an empty string to clear it.",
+  "type": "string"
+}
  2. Changed5 schema fields changedv0.9.2
    • changedInput schema / properties / requestBody / properties / transfer / properties / transfer_options / description
      Previous value: -"Where to transfer the call and under what condition. The first matching condition wins."New value: +"Where to transfer the call and under what condition. The first matching condition wins. In an agent update, sending this list replaces all saved options. Omit it to keep them unchanged, or send an empty array to clear them."
    • addedInput schema / properties / requestBody / properties / voice / dependentRequired
      Added value: +{
+  "provider": [
+    "voice_id"
+  ]
+}
    • changedInput schema / properties / requestBody / properties / voice / description
      Previous value: -"Configuration for the text-to-speech voice."New value: +"Configuration for the text-to-speech voice. `provider` and `voice_id` identify the voice together, so send both to change it. `provider` on its own is not accepted, and a `voice_id` on its own leaves the voice as it was. The other fields here apply independently."
    • changedInput schema / properties / requestBody / properties / voice / properties / provider / description
      Previous value: -"The voice provider to use. The current catalog is returned by the TTS providers list."New value: +"The voice provider to use. The current catalog is returned by the TTS providers list. Send `voice_id` alongside it."
    • changedInput schema / properties / requestBody / properties / voice / properties / voice_id / description
      Previous value: -"The provider's voice identifier, returned in the `name` field of the voices list (not the numeric `id`)."New value: +"The provider's voice identifier, returned in the `name` field of the voices list (not the numeric `id`). Takes effect when `provider` is sent alongside it."
  3. First observedv0.9.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations (readOnlyHint=false) already establish this is a write operation, and the description's 'Update' is consistent. Beyond annotations, it adds genuine behavioral context: partial PATCH-like semantics (omitted fields are preserved) and the account-level access gate on voicemail detection, which would otherwise cause confusing failures. It doesn't mention effects on in-flight calls or reversibility, but the disclosed traits are the most decision-critical ones.

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?

Two crisp sentences front-load the core action and the partial-update rule, followed by one blockquote that flags the only real-world caveat an agent must know before configuring voicemail. No filler or repetition of schema content.

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

Completeness4/5

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

For a tool with a massive nested schema that is already 100% self-documented and annotations that cover the safety profile, the description fills exactly the gaps the schema cannot express: partial-update behavior and an account-level access prerequisite. The absence of an explicit note on when to use this versus createAgent is a minor gap given the clarity of the verb.

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

Parameters3/5

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

Schema description coverage is 100%, and the requestBody contains detailed per-field descriptions, so the schema carries the documentation load. The description's main semantic contribution is clarifying that requestBody is a partial patch despite being required — genuinely useful, but it only illuminates one aspect of a large parameter surface.

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?

The description states a specific verb and resource: 'Update an existing agent.' The modifier 'existing' and the update semantics clearly differentiate it from sibling tools like createAgent, getAgent, and deleteAgent without ambiguity. It lacks an explicit naming of sibling alternatives, but the purpose is unmistakable.

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

Usage Guidelines3/5

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

It provides direct how-to guidance: 'Send only the fields you want to change,' which communicates the partial-update convention, and the blockquote adds a conditional constraint for the voicemail object (request access first). However, it never explicitly tells the agent when to prefer this over createAgent, createAgentVersion, or restoreAgentVersion, leaving lifecycle routing to inference.

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

Deploy Server

Other Tools