Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_get_group

Read-only

Retrieves group or channel details: title, type, member count, owner, about, and username by ID to help inspect or manage the chat.

Instructions

Get a group or channel's details: title, type, member count, owner, about, username.

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

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup or channel 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 safety is covered. The description adds value by naming the exact fields returned (title, type, member count, owner, about, username), but says nothing about failure modes such as an invalid id or lack of access.

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?

A single front-loaded sentence with a colon-delimited field list — no filler, and the resource is identified before the enumeration.

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?

With no output schema, the field enumeration is genuinely necessary and supplies it; nothing about return shape is left ambiguous. Only the absence of error/access behavior keeps it from a 5 for a simple read tool.

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?

Only one parameter exists and the schema documents it at 100% coverage ('Group or channel id'), which sets the baseline at 3. The description's phrase 'group or channel' reinforces that the same id works for both entity types but adds no new syntax or format detail.

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?

The description gives a specific verb ('Get') and resource ('a group or channel's details') and enumerates the returned fields, so the agent knows exactly what this fetches. It does not explicitly contrast with siblings such as bale_get_user or bale_get_group_invite_link, so it falls 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 Guidelines3/5

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

Usage is only implied: call it with a group id when you need group metadata. There is no statement about when to prefer bale_get_user, bale_list_group_members, or bale_get_group_invite_link, and no preconditions (e.g., membership requirements) are mentioned.

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