Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_join_group

Join a Bale group or channel using an invite link (ble.ir/join/...). Acts on the user's real account, so confirm with the user first unless they already requested this join.

Instructions

Join a group or channel by invite link (ble.ir/join/...). 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": {
      "invite_link": "<invite_link>"
    },
    "name": "bale_join_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_linkYes

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 and openWorldHint=true, so the mutating and external-network nature is covered structurally. The description usefully adds that this acts on the user's real account and needs confirmation, but says nothing about failure modes such as an invalid or expired invite link, or whether joining twice is harmless.

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 action and the input format, then the safety caveat. Nothing is padded, though the parenthetical format example could be folded in more tightly.

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 one-parameter action with no output schema and only partial annotation coverage, the description covers purpose, input format, and the confirmation requirement. The notable remaining gap is error behavior on an invalid or already-used invite link.

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?

With 0% schema description coverage, the description does the compensating work by showing the expected link shape ('ble.ir/join/...'). However, it never clarifies whether a full URL, a short code, or a bare hash is acceptable, which is the main ambiguity for a single required string parameter.

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 concrete verb and resource ('Join a group or channel') plus the mechanism ('by invite link'), which clearly separates it from siblings like bale_create_group or bale_add_group_members. It stops short of naming an alternative outright, so it lands just below the top mark.

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 confirmation policy ('confirm with the user first unless they already asked for exactly this'), which is actionable when-to-use guidance. It does not cover when not to use it (e.g., the user is already a member, or an expired link), so no true alternative routing is present.

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