Skip to main content
Glama

Wipe a conversation to test the bot from scratch

dosai_clear_conversation
Destructive

Reset one conversation so the bot meets this person as a new client: deletes ALL its messages in the cabinet, the leads created from it (with their tasks, reminders and history) and its follow-ups, wipes the collected client data and summary, resets the stage and switches the bot on there. The link to the deal in an external CRM is dropped (the deal itself stays), so the next lead from this person creates a NEW deal there. Messages scheduled for later are not removed (dosai_list_scheduled_messages). Meant for the owner's own test chat, not for a real client. The conversation stays in the list; the client's messenger is not touched. Cannot be undone. Two steps. 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_clear_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.
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.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: the CRM deal link is dropped while the deal itself survives so the next lead creates a NEW deal, scheduled messages survive, the conversation stays in the list, the client's messenger is untouched, it cannot be undone, and it requires editor role. That is exactly the collateral-damage profile an agent needs before invoking a destructive tool.

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 destructive scope is front-loaded in the first sentence and every following clause carries non-redundant information (exclusions, irreversibility, role, step count). The single long enumeration sentence is dense to parse, but nothing is filler.

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?

For a destructive, non-read-only mutation with no output schema, the description covers consequences, preserved state, irreversibility, authorization and the confirmation flow. An agent has everything needed to decide whether to call and how to call it safely.

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% and the confirm_token property already documents the first-call/second-call protocol and its purpose, so the description's "Two steps" only corroborates rather than adds. The description contributes no format or sourcing detail beyond what project_id and conversation_id already carry in the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Reset one conversation") plus the exact scope of the reset: messages in the cabinet, leads with tasks/reminders/history, follow-ups, collected data and summary, stage, bot switch. It explicitly distinguishes itself from dosai_list_scheduled_messages for scheduled messages, so an agent can tell what this does and does not cover.

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?

"Meant for the owner's own test chat, not for a real client" is an explicit when-to-use and when-not-to-use rule, and it names the neighboring tool responsible for scheduled messages. The two-step confirm requirement is also spelled out, so the agent knows this is not a one-shot call.

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