Skip to main content
Glama
Sign In
bale-mcp

bale-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Bot: edit message

bot_edit_message
Destructive

Modify the text of a message the bot already sent in a Bale chat by supplying the chat ID, message ID, and replacement text. Use it to correct or update bot output, and confirm with the user first.

Instructions

Replace the text of a message the bot sent earlier. Changes a real message; confirm with the user first.

Input Schema

NameRequiredDescriptionDefault
textYesNew text.
chat_idYesChat id (number, e.g. 123456789) or public '@channel' username. See bot_list_chats.
message_idYesId of a text message the bot sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • changedInput schema / properties / chat_id / description
      Previous value: -"Chat id (number from bot_get_new_messages or bot_list_chats, e.g. 123456789) or a public channel/group username like '@mychannel'."New value: +"Chat id (number, e.g. 123456789) or public '@channel' username. See bot_list_chats."
    • removedInput schema / properties / chat_id / title
      Removed value: -"Chat Id"
    • removedInput schema / properties / message_id / title
      Removed value: -"Message Id"
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • removedInput schema / title
      Removed value: -"bot_edit_messageArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "bot_edit_messageDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds a genuine extra: a user-confirmation requirement and the constraint that only bot-sent messages can be edited. It omits anything about the old text being lost or platform edit limits.

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?

Two short sentences, purpose front-loaded, no filler. 'Changes a real message' partially restates what the destructive annotation already conveys, but 'confirm with the user first' earns its place.

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 three-parameter mutation with full schema coverage and no output schema, the description covers purpose, scope, and the safety caution. Missing only edge-case behavior such as what happens to the replaced text or failure conditions, which is a minor gap.

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 100% and each of the three parameters is documented in-schema, including the chat_id cross-reference to bot_list_chats. The description adds no format or constraint detail beyond what the schema already provides, so baseline 3 applies.

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 (replace) and resource (text of a message the bot sent earlier), with a scope constraint that rules out editing user-authored messages. It implicitly distinguishes itself from bot_send_message and bot_delete_message, but never names an alternative explicitly.

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

Usage Guidelines2/5

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

The only guidance is a caution to confirm with the user first; there is no statement of when to edit versus delete or re-send, nor prerequisites such as needing a message_id the bot previously produced. Usage must be inferred from the purpose sentence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools