Skip to main content
Glama
AiAgency-Now

VoiceAI-MCP-VAVicky

Official
by AiAgency-Now

update_assistant

Modify an existing VoiceAI assistant's configuration, including name, prompt, AI model, and voice/text settings for customized AI interactions.

Instructions

Update an existing assistant

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assistant_idYesAssistant ID
nameNoAssistant name
apiKeyNoOpenAI API Key
welcome_messageNoWelcome message
promptNoInstructions/Prompt
activeNoWhether assistant is active
assistant_typeNo
ai_platformNo
openai_modelNoAI Model
openai_temperatureNoAI Temperature (0-2)
booking_botNoIs booking bot
locationNoGoHighLevel Location
calendarNoCalendar ID
timezoneNoTimezone
custom_fieldNoCustom field

Implementation Reference

  • Handler logic for the 'update_assistant' tool: prepares and sends a PATCH request to the backend API to update the assistant identified by assistant_id with the provided parameters, filtering empty values.
    case 'update_assistant':
      url = `${this.baseUrl}/assistants/${args.assistant_id}`;
      method = 'PATCH';
      const { assistant_id, ...updateData } = args;
      body = this.filterEmptyValues(updateData);
      break;
  • Schema definition for the 'update_assistant' tool, including input parameters and validation rules, provided in the listTools response.
    {
      name: 'update_assistant',
      description: 'Update an existing assistant',
      inputSchema: {
        type: 'object',
        properties: {
          assistant_id: { type: 'string', description: 'Assistant ID' },
          name: { type: 'string', description: 'Assistant name' },
          apiKey: { type: 'string', description: 'OpenAI API Key' },
          welcome_message: { type: 'string', description: 'Welcome message' },
          prompt: { type: 'string', description: 'Instructions/Prompt' },
          active: { type: 'boolean', description: 'Whether assistant is active' },
          assistant_type: { type: 'string', enum: ['Text Only', 'Voice Only', 'Text & Voice', 'Voice & Text'] },
          ai_platform: { type: 'string', enum: ['openai', 'gemini', 'openrouter', 'deepseek'] },
          openai_model: { type: 'string', description: 'AI Model' },
          openai_temperature: { type: 'number', description: 'AI Temperature (0-2)' },
          booking_bot: { type: 'boolean', description: 'Is booking bot' },
          location: { type: 'string', description: 'GoHighLevel Location' },
          calendar: { type: 'string', description: 'Calendar ID' },
          timezone: { type: 'string', description: 'Timezone' },
          custom_field: { type: 'string', description: 'Custom field' }
        },
        required: ['assistant_id']
      }
    },
  • Utility function that removes undefined, null, and empty string values from the update data object before sending the API request.
    filterEmptyValues(obj) {
      const cleaned = {};
      for (const [key, value] of Object.entries(obj)) {
        if (value !== undefined && value !== null && value !== '') {
          cleaned[key] = value;
        }
      }
      return cleaned;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states it's an update operation (implying mutation) but doesn't describe what happens on success/failure, whether changes are reversible, permission requirements, rate limits, or response format. This is inadequate for a mutation tool with 15 parameters.

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 extremely concise (4 words) and front-loaded with the essential action and resource. There's zero wasted language, making it efficient for quick scanning while still conveying the core purpose.

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

Completeness2/5

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

For a complex mutation tool with 15 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'update' entails operationally, what fields are optional/required beyond assistant_id, or what the tool returns. The high parameter count and mutation nature demand more contextual information than provided.

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 high (87%), so the schema already documents most parameters well. The description adds no additional parameter context beyond implying updates are possible, which doesn't compensate for the 13% coverage gap. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 clearly states the action ('Update') and resource ('an existing assistant'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create_assistant' (creates new) and 'delete_assistant' (removes), but doesn't specify what aspects can be updated beyond the general concept.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing assistant ID), when not to use it, or how it differs from similar tools like 'update_openai_token' or 'update_gemini_token' which might update specific assistant properties.

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/AiAgency-Now/MCP-VoiceAI-WhiteLabel'

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