Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_delete_message

DestructiveIdempotent

Delete a Bale message from your account using chat ID, message ID, and date_ms; set for_everyone=false to remove it only on your side.

Instructions

Delete a message (needs its date_ms from bale_read_chat). for_everyone=false deletes only on your side. Cannot be undone. 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>",
      "date_ms": "<date_ms>"
    },
    "name": "bale_delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesChat id from bale_list_chats (user, group or channel id).
date_msYesThe message's date_ms.
chat_typeNoChat type. Optional if the chat appeared in bale_list_chats before.
message_idYesMessage id.
for_everyoneNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, yet the description still adds useful behavior: irreversibility ("Cannot be undone"), that it operates on the user's real account, and the user-confirmation gate. It does not address permission requirements for deleting for others in groups/channels, which is the main remaining behavioral gap.

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?

Three short sentences, front-loaded with the action and its prerequisite, then the destructive semantics, then the confirmation rule. Every clause carries information an agent needs before calling; nothing is redundant.

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, no-output-schema tool, the description covers the prerequisite, the scope option, irreversibility, and the confirmation policy — enough for correct invocation. The only unstated detail is elevated-permission behavior in groups, which is minor relative to what is provided.

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 100%, so the baseline is 3, but the description goes beyond it by explaining the practical effect of for_everyone=false ("deletes only on your side") and by tying date_ms to its origin in bale_read_chat. That gives the parameter real-world meaning the schema's one-line descriptions do not.

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 ("Delete a message") and immediately attaches the non-obvious prerequisite that callers must first obtain date_ms from bale_read_chat. That prerequisite plus the explicit scope toggle distinguishes it cleanly from siblings like bale_edit_message, bale_forward_message, and bale_read_chat.

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 a concrete confirmation policy ("confirm with the user first unless they already asked for exactly this") and points to bale_read_chat as the source of a required field. It stops short of naming an alternative action for cases where the user actually wanted to modify rather than remove a message, so it is clear context without explicit exclusions.

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