Skip to main content
Glama

Switch the bot on or off in one dialog

dosai_toggle_bot_in_conversation
Destructive

FLIPS the bot in one dialog: on becomes off, off becomes on. Read dosai_get_conversation first (field ai_on) so you flip in the right direction; the answer returns the new ai_on. Switching off is how an owner takes a client over personally. For staff who must NEVER get bot replies (teachers, managers), use dosai_add_never_bot_numbers instead: it also covers numbers that have not written yet. Switching the bot ON in a dialog whose number is on that list takes the number off the list (answer: removed_from_never_bot_list). Requires editor 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>",
      "conversation_id": "<conversation_id>"
    },
    "name": "dosai_toggle_bot_in_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
conversation_idYesFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Conversation id, as returned by dosai_list_conversations."New value: +"From dosai_list_conversations."
  2. 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."
  3. Changed2 schema fields changed
    • removedInput schema / properties / conversation_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)$"
    • 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)$"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag it as a non-read-only, destructive, closed-world operation. The description adds context annotations cannot: the editor role requirement, the return payload (new ai_on), and the non-obvious side effect that switching the bot on can remove a number from the never-bot list (answer: removed_from_never_bot_list). That is real behavioral value beyond the structured data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core flip semantics and routes to the prerequisite read tool immediately. Subsequent sentences each carry distinct information (side effect, alternative tool, role requirement), though the density is high and could be split for easier scanning.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the return value and the special removed_from_never_bot_list answer. Combined with the role requirement and the prerequisite read step, an agent has everything needed to invoke it correctly.

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?

With two parameters and 100% schema description coverage, the schema already explains where project_id and conversation_id come from. The description adds the notion of a single dialog scope but no format or constraint detail beyond the schema, so it sits at the documented baseline.

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 names a specific action (FLIPS) on a specific resource (the bot in one dialog) and spells out the exact semantics: 'on becomes off, off becomes on.' It also distinguishes itself from dosai_add_never_bot_numbers, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

It gives explicit sequencing ('Read dosai_get_conversation first (field ai_on) so you flip in the right direction'), names the alternative for staff who must never get bot replies, and describes the operational scenario ('Switching off is how an owner takes a client over personally'). When-to-use and when-to-use-something-else are both covered.

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