Skip to main content
Glama

Delete a sent message from the conversation history

dosai_delete_message
Destructive

Remove a message the business sent (by the bot or an operator) from the history in the cabinet. ONLY there: the client keeps the message in his messenger, it cannot be withdrawn from his phone. Outgoing messages only, not older than 24 hours. Message ids: dosai_get_messages. 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>",
      "message_id": "<message_id>"
    },
    "name": "dosai_delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes
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. Changed3 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 / message_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 flag destructiveHint=true, but the description adds the crucial real-world consequence: the removal applies only to the cabinet history and 'the client keeps the message in his messenger, it cannot be withdrawn from his phone'. It also discloses the 24-hour limit, the outgoing-only restriction, the editor-role requirement, and the two-step confirmation, which is exactly the extra context annotations cannot convey.

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?

Extremely dense and front-loaded: the destructive scope comes first, then the caveat about the client's copy, then eligibility limits, then id source, then role. Short telegraphic sentences are used but none are wasted or redundant.

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 4-parameter mutation with no output schema, the description covers scope, eligibility limits, permissions, id provenance, and the confirmation protocol. It does not say what the successful response or the failure modes look like (e.g., a message outside the 24-hour window), a minor residual gap given there is no output schema to lean on.

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?

With 75% schema coverage the baseline is 3, and the description raises it by documenting the otherwise-undescribed message_id source ('Message ids: dosai_get_messages') and by flagging that invocation is a two-step confirm flow. It adds no format or validation detail beyond that, so it sits just above 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?

States a specific verb and resource ('Remove a message the business sent... from the history in the cabinet') and immediately scopes it with 'ONLY there' plus 'Outgoing messages only, not older than 24 hours'. An agent can distinguish this from dosai_get_messages, dosai_edit_message, or dosai_cancel_scheduled_message without opening any schema.

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 concrete preconditions: 'Requires editor role', respects a 24-hour window, outgoing-only, and points to dosai_get_messages as the id source. The 'Two steps' note plus the schema's confirm_token flow spells out the invocation sequence. It stops short of naming sibling alternatives explicitly (e.g., editing vs deleting), so it lands at 4 rather than 5.

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