Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_leave_group

Destructive

Leave a Bale group or channel from a real user account; confirm with the user first unless they already requested this action.

Instructions

Leave a group or channel. 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": {
      "group_id": "<group_id>"
    },
    "name": "bale_leave_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds genuinely new context: the action affects the user's real account and requires explicit confirmation, which is exactly the policy an agent needs before a destructive call. It does not explain consequences such as losing membership history or whether rejoining is possible.

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 short sentences with zero waste; the resource comes first and the confirmation constraint follows immediately.

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 destructive tool with annotation coverage and no output schema, the definition is nearly sufficient — purpose, account impact, and confirmation policy are all present. Only post-call effects (what the user loses, whether rejoin is possible) are omitted.

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% and the single group_id parameter is already documented. The phrase 'group or channel' slightly broadens what identifier is acceptable, but that is the only meaning added beyond the schema, so baseline 3 applies.

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 ('Leave a group or channel') that is unambiguous and naturally contrasted with join_group and create_group among the siblings. An agent can identify the operation without opening the 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: confirm with the user first unless the request was exactly this. That is real when-to-use guidance, though it stops short of naming alternatives or what to do if the user is unsure.

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