Skip to main content
Glama

create_assistant

Create a new AI assistant. Required: name, voice_id, language_id, type, mode, timezone, initial_message, system_prompt, and either llm_model_id (pipeline) or multimodal_model_id (multimodal/dualplex). For multimodal/dualplex, knowledgebase_mode must be "function_call" when a knowledgebase is attached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
nameYesDisplay name of the assistant (max 255 chars)
typeYesAssistant call direction
toolsNo
recordNo
fillersNo
timezoneYesIANA timezone, e.g. "Europe/Berlin"
tool_idsNo
voice_idYesVoice ID from get_voices
folder_idNoFolder to place the assistant in (one folder per assistant). See list_folders. Send null to remove.
label_idsNoLabel IDs to tag the assistant with (an assistant can carry multiple labels). See list_labels.
variablesNo
language_idYesPrimary language ID from get_languages
webhook_urlNo
llm_model_idNoRequired for mode=pipeline
max_durationNo
ringing_timeNo
speech_speedNo
ambient_soundNo
endpoint_typeNo
filler_configNo
system_promptYesSystem prompt defining behavior
initial_messageYesFirst message spoken at call start (max 200 chars)
llm_temperatureNo
phone_number_idNo
voice_stabilityNo
knowledgebase_idNo
post_call_schemaNo
voice_similarityNo
is_webhook_activeNo
wait_for_customerNo
knowledgebase_modeNo
voice_mail_messageNo
allow_interruptionsNo
min_interrupt_wordsNo
multimodal_model_idNoRequired for mode=multimodal/dualplex
reengagement_promptNo
tts_emotion_enabledNo
ambient_sound_volumeNo
chat_llm_fallback_idNo
endpoint_sensitivityNo
max_silence_durationNo
post_call_evaluationNo
end_call_on_voicemailNo
interrupt_sensitivityNo
reengagement_intervalNo
secondary_language_idsNoAdditional language IDs the assistant can speak
synthesizer_provider_idNo
transcriber_provider_idNo
turn_detection_thresholdNo
enable_noise_cancellationNo
conversation_ended_retriggerNo
include_recording_in_webhookNo
max_initial_silence_durationNo
conversation_ended_webhook_urlNo
send_webhook_only_on_completedNo
conversation_inactivity_timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
messageNo

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a mutating action. The description adds conditional requirements but does not disclose side effects, authorization needs, or limits. With annotations present, the description provides marginal added value.

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 with two focused sentences. No filler or redundancy; every word earns its place.

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?

Given the complexity (57 parameters, nested objects) and low schema coverage, the description is far from complete. It omits many important parameters and only hints at mode-dependent fields. The output schema exists but is not referenced.

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

Parameters2/5

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

Schema description coverage is only 21%, and the description only covers a handful of the 57 parameters. It explains the condition for llm_model_id vs multimodal_model_id and knowledgebase_mode, but leaves most parameters undocumented. This is insufficient to compensate for the low schema coverage.

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 'Create a new AI assistant' with specific required parameters and conditional requirements. It distinguishes from sibling 'update_assistant' by focusing on creation, and the purpose is precise.

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?

The description provides usage context by listing required fields and conditional rules (e.g., which model ID is required per mode). It does not explicitly state when not to use it or compare with siblings, but the guidance is clear enough for most cases.

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.

TDQS

B3.2/5.0
Disambiguation4/5

Most tools target distinct resources and actions clearly (e.g., create_assistant vs create_campaign). However, there is some overlap like get_outbound_assistants vs get_assistants and list_all_phone_numbers vs get_phone_numbers, causing minor ambiguity.

Naming Consistency4/5

Tools follow a consistent verb_noun pattern with underscores (e.g., create_document, delete_label, get_voices). Only minor deviations exist, such as generate_ai_reply and list_all_phone_numbers, but overall the pattern is maintained.

Tool Count2/5

With 75 tools, the server is excessively large. Although the domain is broad (assistants, calls, messaging, etc.), the number of tools makes it difficult for agents to navigate and select the correct one, reducing coherence.

Completeness4/5

The tool set covers CRUD operations for most resources, plus webhooks, AI replies, and reference data fetching. Minor gaps exist (e.g., no delete_conversation, no attach phone number to assistant), but the surface is largely comprehensive for the platform's purpose.