Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_get_group_invite_link

Read-only

Retrieve a Bale group or channel invite link by providing its group ID, enabling you to share access with others.

Instructions

Get the invite link of a group or channel you can invite to.

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

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup id.

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=true and openWorldHint=true, so the safety profile is covered structurally. The description adds one piece of behavioral context — the group must be one you are permitted to invite to — but says nothing about what happens on a permission failure or whether an existing link is returned versus a new one created.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource and its constraint front-loaded; there is no filler. It is efficient, though it is close to the minimum and could have carried one more clause of guidance at no structural cost.

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 single-parameter read tool with no output schema, the description states what is returned (the invite link) and which target chats qualify, which is sufficient to call it correctly. The only real gap is the unaddressed error/permission-failure behavior, which is minor here.

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?

With a single required parameter and 100% schema description coverage, the schema already carries the parameter meaning. The description's mention of 'group or channel' loosely aligns with the integer-or-string group_id but adds no format, example, or resolution guidance beyond the schema baseline.

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 names a specific verb and resource ('Get the invite link') and scopes it to 'a group or channel', which is enough to tell it apart from siblings like bale_get_group or bale_join_group. It stops short of explicitly naming an alternative tool, so it lands at clear-but-not-differentiating.

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 phrase 'you can invite to' implies a precondition (you must have invite rights in that chat), but the description never states when to use this versus listing chats or fetching group details. Usage is implied rather than spelled out, and no exclusions or failure conditions are given.

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