Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_list_group_members

Read-only

Lists members of a Bale group or channel with names and admin flags, helping you identify participants; requires permission to view members.

Instructions

List members of a group or channel (with names and admin flags). Needs permission to see members.

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_list_group_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50.
group_idYesGroup id.

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=true and openWorldHint=true, so the safety profile is covered. The description adds a real access constraint (member-visibility permission) and hints at returned fields, but says nothing about pagination behavior or result ordering despite a limit parameter being present.

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 core action and the returned fields front-loaded ahead of the permission caveat. Nothing could be removed without losing information.

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 simple two-parameter read tool with no output schema, the description covers purpose, access requirement, and the shape of the results, which is enough to call it correctly. The only gap is pagination guidance for the 500-max limit.

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% (group_id documented, limit documented with 'Default 50'), so the schema carries the parameter burden. The description adds no syntax detail about the polymorphic integer-or-string group id, which is the one place where extra meaning would have helped.

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 ('List members of a group or channel') and even previews the payload ('names and admin flags'), which clearly separates it from bale_add_group_members, bale_remove_group_member, and bale_get_group. It stops short of naming a sibling or contrasting scope, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The prerequisite 'Needs permission to see members' tells the agent when the call can succeed, which is useful. There is no explicit guidance on when to pick this over bale_get_group or bale_list_chats, or what to do when permission is missing, so usage is only implied.

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