Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_forward_message

Forwards a Bale message from one chat to another using message ID and date_ms, requiring user confirmation because it acts on the real account.

Instructions

Forward a message to another chat (needs the message's date_ms). 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": {
      "from_chat_id": "<from_chat_id>",
      "message_id": "<message_id>",
      "date_ms": "<date_ms>",
      "to_chat_id": "<to_chat_id>"
    },
    "name": "bale_forward_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_msYesThe message's date_ms.
message_idYesMessage id.
to_chat_idYesChat id from bale_list_chats (user, group or channel id).
from_chat_idYesChat id from bale_list_chats (user, group or channel id).
to_chat_typeNoChat type. Optional if the chat appeared in bale_list_chats before.
from_chat_typeNoChat type. Optional if the chat appeared in bale_list_chats before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation and external-visibility profile is known. The description usefully adds that it operates on the user's real account and requires confirmation, plus the date_ms dependency, but says nothing about failure modes, reversibility, or what happens if the message reference is stale.

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, front-loaded with the core action and the mandatory key parameter, followed by the safety caveat. Every clause carries weight, with only minimal redundancy against the schema's date_ms description.

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?

With six parameters, full schema coverage, and annotations covering the safety profile, the description supplies the only missing behavioral piece an agent needs before calling: the user-confirmation requirement. No output schema exists, so return values are out of scope, and nothing critical appears to be missing.

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 100%, including enum descriptions for chat types and the note that types are optional if the chat came from bale_list_chats, so the schema carries parameter meaning. The description only restates that date_ms is needed, adding no syntax, format, or edge-case detail beyond the schema; 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 and resource ('Forward a message to another chat'), which is unambiguous and clearly distinct from bale_send_message or bale_edit_message by the verb alone. It does not explicitly name or contrast with a sibling, so it stops short of 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 concrete when-to-use context: it acts on the user's real account, so the agent is told to confirm with the user first unless the user already requested exactly this. That is actionable gating guidance, though it never names alternatives or exclusions relative to sibling tools.

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