Skip to main content
Glama

SiteSpeak Chatbot Manager

by ai.sitespeak.api

Update Chatbot Settings Tool

update_chatbot_settings

Update a chatbot's settings. Only the fields you pass are changed. Call get_chatbot first to see allowed_models before changing gpt_model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topKNoRetrieved-chunk count 1-3.
gpt_modelNoLLM model id. Must be one of the chatbot's allowed_models.
chatbot_idYesThe chatbot id.
temperatureNoSampling temperature 0-2.
history_countNoConversation history turns 0-10.
default_answerNoFallback answer when the bot cannot answer.
welcome_messageNoWelcome message (max 500 chars). Separate multiple bubbles with a blank line.
escalations_emailNoSemicolon-separated email addresses notified on escalation.
enable_escalationsNoTurn human-handoff escalations on/off.
enable_lead_captureNoTurn the lead-capture form on/off.
instructions_promptNoSystem/instructions prompt (max 20000 chars).
lead_capture_fieldsNoLead-capture field definitions {type,name,required,enabled,order}. Required when enabling lead capture.
escalate_message_thresholdNoMessages before a human handoff is offered (1-10).
enable_escalations_round_robinNoRotate escalation emails round-robin across the addresses.
enable_escalations_notificationNoEmail a notification when a conversation escalates.

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions the partial update behavior but lacks details on authentication, rate limits, response format, or error handling. The disclosure is minimal beyond what the schema already provides.

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 sentences, front-loaded with the key point of partial update. Every word earns its place. No fluff.

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 15 parameters, no output schema, and no annotations, the description is sparse. It explains the partial update and one prerequisite but omits return values, error conditions, and other behavioral context needed for a comprehensive update tool.

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 coverage is 100%, so baseline is 3. The description does not add meaningful semantic information beyond the schema descriptions; it only reiterates the requirement for gpt_model consistency, which is already in the schema.

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 the tool updates chatbot settings and uses a partial update pattern ('Only the fields you pass are changed'). It distinguishes from sibling tools like get_chatbot or other update tools.

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 explicitly advises calling get_chatbot first to check allowed_models before changing gpt_model, providing a specific usage guideline. It does not explicitly list when not to use or alternative tools, but the guidance is strong.

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

All SiteSpeak Chatbot Manager toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (sources, suggested messages, chatbots, inbox, leads, analytics, insights). There is no ambiguity between tool purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (add_, get_, list_, recrawl_, update_). The naming convention is uniform and predictable.

Tool Count5/5

15 tools is well-scoped for a chatbot manager. The set covers all key functional areas without being excessive or insufficient.

Completeness3/5

The tool surface is largely complete but lacks delete operations: there is no 'remove_suggested_message' (though referenced in a description) and no way to delete a source. These are notable gaps.

Resources