Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_edit_message

DestructiveIdempotent

Edits the text of a sent message on Bale, requiring user confirmation unless the edit was already requested.

Instructions

Edit the text of a message you sent. Acts on the user's real account: confirm with the user first unless they already asked for exactly this.

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": {
      "chat_id": "<chat_id>",
      "message_id": "<message_id>",
      "text": "<text>"
    },
    "name": "bale_edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
chat_idYesChat id from bale_list_chats (user, group or channel id).
chat_typeNoChat type. Optional if the chat appeared in bale_list_chats before.
message_idYesMessage id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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=true and openWorldHint=true, so the safety profile is structured. The description adds genuine context the annotations lack: it mutates the user's real account and therefore warrants confirmation. It does not cover failure modes (non-editable messages, permission limits) or return behavior, so a 3 is fitting.

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?

Two sentences, zero waste, with the operation stated first and the confirmation constraint immediately after. Nothing is repeated from the annotations or schema.

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 4-parameter mutation tool with no output schema, the definition covers what it does, whose account it touches, and the confirmation requirement. Only edge cases (what happens if the message cannot be edited, whether only your own messages qualify as a hard error) are left unstated.

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 75% and chat_id, chat_type and message_id all carry schema descriptions, so the schema does most of the work. The description only implicitly clarifies that 'text' is the replacement content for an existing message. That is a small addition, matching the baseline for a well-covered schema.

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 and resource ('Edit the text of a message') plus a meaningful scope restriction ('you sent'), which separates it from bale_send_message and bale_delete_message without naming them. It stops short of an explicit sibling comparison, so a 4 rather than a 5.

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 an explicit gating rule: confirm with the user first unless they already asked for exactly this. The 'message you sent' qualifier also implies when the tool is inapplicable. It does not point to alternatives (e.g., sending a new message instead), so it falls short of the top band.

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