Skip to main content
Glama
bale-account-mcp

bale-account-mcp

by AliMilani

bale_find_contact

Read-only

Find a Bale user or group by phone number and retrieve its ID so you can send messages to the correct contact.

Instructions

Find a Bale user (or group) by phone number, to get an id you can message.

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": {
      "phone": "<phone>"
    },
    "name": "bale_find_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYese.g. 989121234567 or 09121234567

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 and the description only needs to add context. It usefully discloses the result's role (an id for messaging) but says nothing about failure modes, whether groups and users resolve identically, or how partial or ambiguous numbers are handled.

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 sentence with no filler; the resource, the key parameter, and the reason for calling are all front-loaded. 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 single-parameter, read-only lookup with full schema coverage and no output schema, the description covers what the tool does and why. The only meaningful gap is absent guidance on unresolved or ambiguous phone numbers and on differentiating it from the similar bale_get_user sibling.

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% and the single phone parameter is documented with two concrete format examples (989121234567 / 09121234567) in the schema itself. The description only restates "by phone number", adding no format or normalization guidance beyond the schema, which is the correct baseline 3.

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 ("Find a Bale user (or group) by phone number") and adds the downstream purpose ("to get an id you can message"). It does not distinguish itself from the sibling bale_get_user or bale_list_contacts, so an agent cannot fully rule out overlap from the description alone.

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 implied by the phrase "to get an id you can message", which tells the agent this is a resolution step preceding bale_send_message. However, there is no explicit when-to-use vs. bale_get_user, no mention of what to do if the lookup fails or returns multiple matches, and no prerequisites stated.

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