Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_create_group

Create a Bale group or channel and optionally add users; set a username to make it public. Confirm before acting on the user's real account unless they already requested it.

Instructions

Create a group or channel, optionally adding users. A username makes it public. 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": {
      "title": "<title>"
    },
    "name": "bale_create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoDefault group.
titleYes
user_idsNoUsers to add.
usernameNoPublic username (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds the important consequence that this acts on the user's real account, mandates confirmation, and warns that a username makes the group public — disclosure the annotations do not provide. It still says nothing about who becomes admin or what happens on name collisions.

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, capability first and the safety constraint front-loaded in the second. Every clause carries information; nothing is padding.

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 4-parameter mutation tool with no output schema, it covers the essential risk profile (real account, confirmation, public visibility). An agent could call it correctly, though the return value and post-creation state remain unspecified.

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 75% and the description adds meaning beyond it: it ties user_ids to the 'optionally adding users' behavior and explains that username makes the group public. The type parameter's group-vs-channel distinction is left entirely to the schema's default note.

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 specific verb and resource ('Create a group or channel') plus an optional capability ('optionally adding users'), which cleanly separates it from bale_add_group_members or bale_get_group. It stops short of naming a sibling to route against, so it lands just under 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 a concrete, actionable condition: confirm with the user first unless they already asked for exactly this. That is real when-to-use guidance. It does not point to alternatives for follow-up actions (for example adding members later), so it is not exhaustive.

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