Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_send_file

Send a local file from allowed directories to a Bale chat as a document, photo, video, audio, voice, or GIF, with an optional caption.

Instructions

Send a local file (absolute path inside BALE_SEND_DIRS) as a document, photo, video, audio, voice or gif, with an optional caption. 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>",
      "path": "<path>"
    },
    "name": "bale_send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoDefault: photo for images, otherwise document.
pathYesAbsolute path.
captionNo
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description adds meaningful context beyond that — that the action is performed on the user's real account, requires confirmation, and that paths are confined to BALE_SEND_DIRS. It stops short of saying what the call returns or how delivery failures/size limits behave, so it is not exhaustive.

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, no filler. The capability and its source restriction come first, the confirmation requirement second — well front-loaded for a scanning agent.

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 five-parameter, non-destructive send tool with 80% schema coverage and no output schema, the description supplies the operational essentials: what it sends, where files may come from, and the confirmation norm. Only the absence of any note on return value or failure modes keeps it below complete.

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 80%, so the schema carries most parameter meaning. The description still adds the non-obvious constraint that 'path' must be an absolute path inside BALE_SEND_DIRS, which the schema alone does not state, plus the caption/media-type framing. The chat_id/chat_type coupling is left entirely to the schema.

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 ('Send') and resource ('a local file') plus the full set of renderable media types (document, photo, video, audio, voice, gif) and the optional caption. It also names the source restriction (BALE_SEND_DIRS), so an agent can distinguish this from text-sending siblings like bale_send_message without opening a schema.

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 precondition: act only after user confirmation unless the user already asked for exactly this. That is real when-to-use guidance. It does not, however, route the agent toward a sibling for the adjacent case (sending text vs. a file), so it falls short of a 5.

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