Skip to main content
Glama

Correct a sent message in the history

dosai_edit_message
Destructive

Change the text of a message the business sent, in the conversation history of the cabinet ONLY: the client keeps the original text in his messenger. Outgoing messages only, not older than 24 hours, up to 4000 characters. To really correct yourself, send a new message (dosai_send_operator_message). 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>",
      "text": "<text>"
    },
    "name": "dosai_edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
message_idYes
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. 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.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuinely useful context beyond that: the client keeps the original text, so this edit is cosmetic for internal history, plus the 24-hour window and editor-role requirement. It stops short of what happens on an expired message (error type) or whether the edit is visible to other agents in the cabinet.

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?

Front-loaded with the most surprising fact (cabinet-only effect), then constraints, then the alternative. Dense and mostly waste-free, but the clipped phrasing "in the conversation history of the cabinet ONLY" and stacked comma constraints read telegraphically and could be tightened into clearer clauses.

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-required-parameter mutation with no output schema, the definition covers the essentials: what changes, what does not, eligibility limits, and permissions. Remaining gaps are secondary — failure behavior past 24 hours and the source of message_id.

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?

Schema coverage is 50%, with only project_id and conversation_id documented via "From dosai_list_projects/conversations". The description compensates for message_id by restricting it to messages the business sent and under 24 hours old, which is real added semantics. The 4000-character limit merely restates the schema's maxLength, and it never says where to obtain message_id, so one gap remains.

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?

"Change the text of a message the business sent, in the conversation history of the cabinet ONLY" gives a specific verb (change text), a specific resource (an already-sent outgoing message), and an explicit scope boundary (cabinet history only, not the client's messenger). That scope statement alone distinguishes it from dosai_send_operator_message and dosai_delete_message.

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 names the alternative and the condition that selects it: "To really correct yourself, send a new message (dosai_send_operator_message)." It also states the eligibility preconditions — outgoing messages only, no older than 24 hours, requires editor role — so an agent knows when this tool will refuse.

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