Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_add_group_members

Add specified users to a Bale group or channel you administer; confirm with the account owner before acting unless they already requested it.

Instructions

Add users to 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_ids": "<user_ids>"
    },
    "name": "bale_add_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup id.
user_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 write and external-side-effect profile is partly covered. The description adds genuine value by stating it acts on the user's real account and requires confirmation — behavior an agent would otherwise not know. It still omits whether added users are notified, whether admin rights are checked server-side, and what happens if some ids fail.

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, zero filler, with the action and scope front-loaded and the confirmation rule second. Nothing needs trimming.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers the essential safety story but leaves the return value and error semantics entirely unexplained. An agent still cannot predict success/failure reporting or how to interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: group_id carries the useless gloss "Group id." and user_ids has no description at all. The tool description adds no meaning about either parameter — nothing on id format, whether string or int ids are interchangeable, whether the caller can add themselves, or how partial failures are handled.

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 ("Add users to a group or channel") plus a scope constraint ("you administer"), which cleanly separates it from sibling tools like bale_remove_group_member and bale_list_group_members by implication. It does not explicitly name a sibling it is not, so it stops short of a 5.

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 real precondition (the caller must administer the group/channel) and an explicit confirmation rule: confirm with the user unless they already asked for exactly this. It does not name alternatives such as join_group or create_group, but the when-to-use condition is clear.

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