Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_send_message

Send a text message from your Bale account to a specified chat; long text is split into multiple messages, and real-account actions require confirmation.

Instructions

Send a text message from your account. Long text is split into several messages. 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>",
      "text": "<text>"
    },
    "name": "bale_send_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.
reply_to_date_msNodate_ms of the message being replied to.
reply_to_message_idNoReply to this message (also give reply_to_date_ms).

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?

Adds genuinely useful behavior beyond the annotations: long text is split into several messages (so one call can produce multiple outbound messages), and it acts on the user's real account, warranting confirmation. The annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). However, it does not disclose what happens on failure, whether a message id is returned (relevant for later reply/delete), or reply-target behavior.

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, then the splitting side effect, then the confirmation rule. No filler or restated metadata.

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 5-parameter tool with 80% schema coverage and no output schema, this covers the essential agent-facing concerns: side effects, confirmation, and multi-message splitting. The one gap is that it does not say what the call returns, which matters because the agent may need a message id for follow-up reply or delete calls.

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 80%, so the schema already documents chat_id, chat_type, and the reply parameters. The description only implies the text parameter and its splitting behavior; it adds no syntax or format detail for chat_id, chat_type, or the reply_to_* pairing. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ("Send a text message from your account"), and the word "text" implicitly contrasts with the sibling bale_send_file, which handles files. It stops short of naming any sibling explicitly, so the differentiation is inferable rather than stated.

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 precondition: confirm with the user first unless they already asked for exactly this. That is real when-to-use guidance for a side-effecting tool. It does not mention alternatives such as bale_edit_message or bale_forward_message, which would have made it a 5.

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