neuron

Update Bot

neuron_update_bot

Idempotent

Update an existing bot's configuration. Only provided fields are modified; omitted fields remain unchanged.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Unique identifier (UUID) of the bot to update
`name`	No	New display name for the bot
`llmModel`	No	OpenRouter model ID (e.g., 'deepseek/deepseek-v4.1-flash' (default), 'google/gemini-2.5-flash')
`metadata`	No	Arbitrary metadata object stored with the bot. Replaces the entire metadata field — include ALL existing keys you want to keep. Known keys: 'communityExitFollowUp' (auto-DM users who leave watched groups — { enabled: boolean, groupJids: string[], message: string with {name} placeholder }), 'learningConfig' (self-learning from conversations — { enabled: boolean, folder: string, groupChats: string[], dmPhones: string[], useAdminPhones: boolean }), 'loadBalancing' (multi-channel round-robin — { enabled: boolean, strategy: string }), 'welcomeNewMembers' (fine-tune welcome behavior — { batchWindowSeconds: number, groupJids: string[] }). Additional custom keys are preserved as-is.
`maxTokens`	No	Maximum number of tokens the bot can generate per response
`assignment`	No	One-sentence role definition for the bot (max 2000 chars)
`systemPrompt`	No	New system prompt defining the bot's behavior and personality
`llmTemperature`	No	Temperature parameter controlling response randomness (0 = deterministic, 2 = creative)
`welcomeMessage`	No	Welcome message sent to new members joining groups the bot manages. Setting this field activates the batched welcome feature — new members are accumulated over a window (default 60s) and welcomed in a single message with @mentions. Set to null to disable.
`fallbackMessage`	No	Message sent when the bot cannot understand user input (max 2000 chars)
`greetingMessage`	No	Automatic greeting sent when a new conversation starts (max 2000 chars)
`escalationPrompt`	No	Prompt template used when escalating to a human agent (max 5000 chars)
`responsibilities`	No	Array of responsibility descriptions defining what the bot handles
`whatsappChannelId`	No	Unique identifier (UUID) of the WhatsApp channel to associate with the bot

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / llmModel / description

Previous value: -"OpenRouter model ID (e.g., 'google/gemini-2.5-flash-lite', 'openrouter/auto')"New value: +"OpenRouter model ID (e.g., 'deepseek/deepseek-v4.1-flash' (default), 'google/gemini-2.5-flash')"

Changed2 schema fields changedJul 25, 2026

changedInput schema / properties / metadata / description

Previous value: -"Arbitrary metadata object stored with the bot. Replaces the entire metadata field — include ALL existing keys you want to keep. Known keys: 'communityExitFollowUp' (auto-DM users who leave watched groups — { enabled: boolean, groupJids: string[], message: string with {name} placeholder }), 'learningConfig' (self-learning from conversations — { enabled: boolean, folder: string, groupChats: string[], dmPhones: string[], useAdminPhones: boolean }), 'loadBalancing' (multi-channel round-robin — { enabled: boolean, strategy: string }). Additional custom keys are preserved as-is."New value: +"Arbitrary metadata object stored with the bot. Replaces the entire metadata field — include ALL existing keys you want to keep. Known keys: 'communityExitFollowUp' (auto-DM users who leave watched groups — { enabled: boolean, groupJids: string[], message: string with {name} placeholder }), 'learningConfig' (self-learning from conversations — { enabled: boolean, folder: string, groupChats: string[], dmPhones: string[], useAdminPhones: boolean }), 'loadBalancing' (multi-channel round-robin — { enabled: boolean, strategy: string }), 'welcomeNewMembers' (fine-tune welcome behavior — { batchWindowSeconds: number, groupJids: string[] }). Additional custom keys are preserved as-is."

addedInput schema / properties / welcomeMessage

Added value: +{
+  "description": "Welcome message sent to new members joining groups the bot manages. Setting this field activates the batched welcome feature — new members are accumulated over a window (default 60s) and welcomed in a single message with @mentions. Set to null to disable.",
+  "type": "string"
+}

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / metadata

Added value: +{
+  "additionalProperties": {},
+  "description": "Arbitrary metadata object stored with the bot. Replaces the entire metadata field — include ALL existing keys you want to keep. Known keys: 'communityExitFollowUp' (auto-DM users who leave watched groups — { enabled: boolean, groupJids: string[], message: string with {name} placeholder }), 'learningConfig' (self-learning from conversations — { enabled: boolean, folder: string, groupChats: string[], dmPhones: string[], useAdminPhones: boolean }), 'loadBalancing' (multi-channel round-robin — { enabled: boolean, strategy: string }). Additional custom keys are preserved as-is.",
+  "type": "object"
+}

Changed1 schema field changedJul 9, 2026

changedInput schema / properties / llmModel / description

Previous value: -"OpenRouter model ID (e.g., 'google/gemini-2.5-flash-lite-preview-09-2025', 'openrouter/auto')"New value: +"OpenRouter model ID (e.g., 'google/gemini-2.5-flash-lite', 'openrouter/auto')"

First observedJun 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint=false, idempotentHint=true, and readOnlyHint=false, lowering the burden. The description adds genuinely non-obvious behavior: patch semantics where omitted fields are preserved. It does not, however, mention that the nested metadata field replaces the whole object (only the schema says that), nor any permission requirements.

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 short sentences with zero waste. The core action is front-loaded, and the partial-update caveat follows immediately, so the most decision-relevant information is read first.

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 14-parameter mutation tool with nested objects, the rich 100%-covered schema and the idempotent/non-destructive annotations carry most of the load, and there is no output schema to explain. The description supplies the essential patch semantics but omits the metadata full-replacement warning, which arguably matters enough to surface here.

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 the baseline is 3. The description adds an interpretive layer beyond the schema by clarifying that unspecified parameters retain existing values, which changes how the agent populates the 14 fields. It still doesn't flag the metadata-replacement nuance at the description level.

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 clear verb + resource ("Update an existing bot's configuration"), so an agent immediately knows this mutates an existing bot rather than creating or fetching one. It does not name or contrast against siblings like neuron_create_bot, neuron_get_bot, or neuron_delete_bot, but the update semantics are unambiguous.

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?

The line "Only provided fields are modified; omitted fields remain unchanged" effectively tells the agent this is a partial-update (PATCH) tool, which is real usage guidance. However, there is no explicit when-to-use vs alternatives, no prerequisites (e.g., bot must exist), and no exclusions for fields that cannot be combined.

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

All neuron tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?