Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_remove_group_member

Destructive

Remove a specified user from a Bale group or channel you administer by providing the group and user IDs.

Instructions

Remove a user from a group or channel you administer. 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>",
      "user_id": "<user_id>"
    },
    "name": "bale_remove_group_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser id.
group_idYesGroup id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds genuine value by noting the action hits the user's real account and requires confirmation, but says nothing about prerequisites (bot admin status), failure modes, or whether the removal is reversible.

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 action statement comes first and the safety constraint immediately follows, which is the right ordering for a destructive tool.

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 two-parameter destructive tool with full annotation coverage and no output schema, the essentials are present: what is removed, from where, whose account is affected, and that confirmation is expected. It is slightly thin on prerequisites such as bot admin rights in the target group.

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 100%: both group_id and user_id carry inline descriptions and are marked required. The description adds no format, type, or identifier-resolution detail 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?

"Remove a user from a group or channel you administer" gives a specific verb (remove), a specific resource (group member), and a scope qualifier ("you administer") that separates it from self-service operations like bale_leave_group and inverse tools like bale_add_group_members. 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?

The definition states a clear operating condition: confirm with the user first unless the request was explicit. That is actionable guidance for a destructive action, but it names no alternative tool or exclusion case (for example, what to do if admin rights are missing).

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