Skip to main content
Glama

Search contacts on a Beeper account

search_contacts
Read-only

Search contacts on a specific messaging account by name, phone number, email, or @username—including people you have never chatted with—to find their ID for starting a chat.

Instructions

Find people on one account (e.g. WhatsApp, Signal), including people you have never chatted with. A phone number, email or @username is also looked up exactly on the network. Use the returned id with start_chat. Account IDs come from the official Beeper MCP's get_accounts.

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": {
      "accountID": "<accountID>",
      "query": "<query>"
    },
    "name": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesName, phone number (E.164), email or @username
accountIDYesAccount to search, e.g. whatsapp.33612345678

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the search reaches the network rather than only local chat history, and phone/email/@username are matched exactly. It does not mention result ordering or pagination behavior, so it stops short of a 5.

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?

Three tight sentences, front-loaded with what is searched and how far the search reaches, then query forms, then the follow-up and the prerequisite for accountID. Nothing is redundant and each sentence carries distinct 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?

There is no output schema, and the description covers only the `id` field of the response plus how to consume it. That is enough to act correctly, but an agent gets no sense of the other fields a match returns (display name, account, etc.), so it is not fully complete for a tool with no output schema.

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 both required parameters and the limit default are already documented in the schema. The description adds only the nuance that phone/email/@username are exact network lookups; it never mentions `limit`, so it does not meaningfully exceed the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find people on one account'), scopes it to a single account, and spells out the reach ('including people you have never chatted with'), which distinguishes it from any history-based lookup. The concrete examples (WhatsApp, Signal) and accepted query forms make the tool's identity unmistakable.

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

Usage Guidelines4/5

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

Gives clear context: search within one account, and account IDs must come from get_accounts, which prevents a common misuse. It also names the follow-up (use the returned `id` with start_chat). No explicit when-not-to-use guidance is given, which keeps it from a 5.

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