Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_get_user

Read-only

Fetches a Bale user's profile by user ID, returning name, username, bio, contact status, and bot status.

Instructions

Get a user's profile: name, username, bio, whether they are a contact or bot.

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": {
      "user_id": "<user_id>"
    },
    "name": "bale_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser 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 value by listing the profile fields returned, which matters since there is no output schema, but it says nothing about behavior for unknown/deleted user ids or whether the target must be a contact.

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?

One short sentence, front-loaded with the verb and resource, followed by the concrete return fields. No filler wording to trim.

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 annotations covering safety, the definition is nearly complete: it names the source of the id and the fields returned. The remaining gap is edge-case behavior (nonexistent user, permission requirements), which is minor at this complexity.

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 coverage is 100%, so the single user_id parameter is already documented ('User id.'). The description adds no additional semantics, such as where the id comes from (chat participants, contact list) or the difference between the integer and string forms the schema permits. Baseline 3 applies.

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 states a specific verb and resource ('Get a user's profile') and even enumerates the returned fields (name, username, bio, contact/bot status). It does not explicitly distinguish itself from adjacent tools such as bale_me (self) or bale_find_contact (lookup), so sibling differentiation is left implicit.

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: fetch a profile when you already have a user_id. There is no explicit statement about when to prefer bale_me for your own profile or bale_find_contact for locating a user, and no prerequisites mentioned.

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