Skip to main content
Glama

Change bot settings

dosai_update_bot_settings
Destructive

Change one or more bot settings. Only the fields you pass change. This affects how the bot talks to real clients immediately, so confirm the change with the user first. Requires admin or owner role.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "settings": "<settings>"
    },
    "name": "dosai_update_bot_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYes
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed4 schema fields changed
    • addedInput schema / properties / settings / properties / bot_hours_source
      Added value: +{
      +  "description": "With schedule_enabled: business = the bot answers during business_hours, own = during its own schedule (for example only at night).",
      +  "enum": [
      +    "business",
      +    "own"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / settings / properties / business_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "break_end": {
      +          "anyOf": [
      +            {
      +              "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|24:00)$",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "break_start": {
      +          "anyOf": [
      +            {
      +              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "days": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "day": {
      +                "enum": [
      +                  "Пн",
      +                  "Вт",
      +                  "Ср",
      +                  "Чт",
      +                  "Пт",
      +                  "Сб",
      +                  "Вс"
      +                ],
      +                "type": "string"
      +              },
      +              "enabled": {
      +                "type": "boolean"
      +              },
      +              "end": {
      +                "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|24:00)$",
      +                "type": "string"
      +              },
      +              "start": {
      +                "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "day",
      +              "enabled",
      +              "start",
      +              "end"
      +            ],
      +            "type": "object"
      +          },
      +          "maxItems": 7,
      +          "minItems": 7,
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "days"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The business's working hours, set once for the whole project: seven days from Пн to Вс in this order, enabled=false = day off, HH:MM in the project's time zone, end before start = past midnight. Optional lunch break for every working day. null = not set (the bot then only knows hours from the company description). Read the current value with dosai_get_bot_settings first."
      +}
    • changedInput schema / properties / settings / properties / schedule / description
      Previous value: -"All seven days, each once, day as Пн Вт Ср Чт Пт Сб Вс (these exact strings). enabled=false = day off. start/end HH:MM in the project's time zone; start equal to end = round the clock. Read the current schedule with dosai_get_bot_settings first and change only what the owner asked."New value: +"The bot's own hours, used when bot_hours_source is own. Same shape rules as above."
    • changedInput schema / properties / settings / properties / schedule_enabled / description
      Previous value: -"Answer only during working hours (set them with schedule). Outside the hours the bot sends offline_message instead of answering."New value: +"Answer only during set hours (false = round the clock). Which hours: bot_hours_source. Outside the hours the bot sends offline_message instead of answering."
  4. Changed3 schema fields changed
    • addedInput schema / properties / settings / properties / buffer_delay_media_seconds
      Added value: +{
      +  "description": "Same as buffer_delay_seconds when the client started with a photo, voice message or video (they take longer to send). Range 0-120.",
      +  "maximum": 120,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / settings / properties / buffer_delay_seconds / description
      Previous value: -"Seconds the bot waits for the client to finish typing before it answers. Range 0-120."New value: +"Once the client sent a second message, seconds of silence the bot waits for before it answers all of them at once. Every new message restarts the count. Default 7. Range 0-120."
    • addedInput schema / properties / settings / properties / buffer_first_message_seconds
      Added value: +{
      +  "description": "Seconds the bot waits after a single client message in case another one follows, before it starts the reply. Lower = answers faster; higher = less often answers half a thought. If the client writes again while the bot is already writing, the draft is discarded and half of its price is charged. Default 6. Range 0-60.",
      +  "maximum": 60,
      +  "minimum": 0,
      +  "type": "number"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / settings / properties / handoff_reply_text
      Added value: +{
      +  "description": "Your own line for the moment the bot handed the case to a human and had nothing of its own left to say (a notify function fired, the model returned no text). Empty = our line \"Спасибо! Передаю вашу заявку специалисту…\". To say NOTHING at all, use the per-function switch instead (dosai_update_function, silent_after_call).",
      +  "maxLength": 500,
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / settings / properties / engage_mode / description
      Previous value: -"Who the bot answers on WhatsApp (and on Instagram unless instagram_engage_mode is set): all = only people who write for the first time after the channel was connected, existing_too = everyone who writes, old contacts too, ad_gated = only people who came from ads."New value: +"Who the bot answers on WhatsApp (and on Instagram unless instagram_engage_mode is set): all = only people who write for the first time after the channel was connected, existing_too = everyone who writes, old contacts too, except chats where the owner or an operator wrote in the last 7 days, ad_gated = only people who came from ads."
  7. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag a destructive, non-read-only, closed-world write, and the description adds genuinely non-redundant context: it is a patch-style update, it takes effect on live client conversations immediately, and it is gated on admin/owner role. It does not cover whether omitted settings revert or what happens on invalid values, but the added value beyond annotations is substantial.

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?

Four short sentences, no filler: what it does, the partial-update rule, the live-impact warning, then the permission gate. The most consequential fact for an agent's decision is placed 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 destructive write tool with no output schema and a large, well-documented nested settings object, the description supplies the safety-critical facts an agent needs: patch semantics, immediate client-visible effect, confirmation requirement, and role gate. Only the pointer to reading current values first lives in the schema rather than the description.

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 50% (project_id documented, the settings wrapper not), but the nested settings properties are documented exhaustively in the schema, including enums and ranges. The description adds no parameter-level meaning at all, so it sits at the baseline for a schema that already carries the weight.

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?

States a specific verb and resource ("Change one or more bot settings") and immediately clarifies the partial-update semantics ("Only the fields you pass change"), which is the key behavioural distinction for this tool. It does not name the read counterpart (dosai_get_bot_settings) in the description itself, so sibling differentiation is only implicit.

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?

Gives a concrete operational rule ("confirm the change with the user first") and a prerequisite ("Requires admin or owner role"), which is real when-to-use context. It stops short of naming when to use this instead of neighbouring writers such as dosai_update_function or dosai_update_booking_settings.

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.

Resources