Skip to main content
Glama

Messaging: Resolve recipient

messaging_resolve_recipient
Read-onlyIdempotent

Turn a person's name, nickname, phone number or handle into the exact WhatsApp/Instagram/Facebook/Telegram recipient BEFORE sending: searches the user's 1-to-1 chats (ranked by most recent exchange) and contacts. Returns incomplete (lookup could not be fully enumerated; do not send automatically), resolved (one clear match: send immediately with the recommended next tool, no extra confirmation needed when the user already gave the message), ambiguous (several people: ask which one, most recent conversation first) or not_found. Use for 'send a WhatsApp to Julien', 'reply to Marie on Instagram', 'message +33 6…'. Never pass a name as chat_id or user_id.

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": {
      "provider": "<provider>",
      "name": "<name>"
    },
    "name": "messaging_resolve_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHow the user refers to the person: first name, full name, phone number or handle.
inbox_idNoRequired for Facebook: exact personal or PAGE_<id>_INBOX inbox.id from facebook_list_inboxes. Preserves the sending identity. Omit for other providers.
providerYesMessaging provider named by the user. LinkedIn recipients use linkedin_resolve_person + linkedin_start_conversation instead.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Required when the user has several accounts for the provider: pick the one the user named.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / inbox_id
      Added value: +{
      +  "description": "Required for Facebook: exact personal or PAGE_<id>_INBOX inbox.id from facebook_list_inboxes. Preserves the sending identity. Omit for other providers.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "whatsapp",
      -  "instagram",
      -  "telegram"
      -]New value: +[
      +  "whatsapp",
      +  "instagram",
      +  "facebook",
      +  "telegram"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds real substance: the search scope (1-to-1 chats ranked by most recent exchange, plus contacts), the four possible result states, and the operational meaning of each. The 'incomplete – do not send automatically' caveat is a behavioral disclosure the annotations cannot express.

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?

Purpose and sequencing constraint are front-loaded, followed by the outcome taxonomy. Dense but nearly every clause carries information; the single long paragraph could be tightened for scannability, which keeps it just under top marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return semantics – and it does, by defining the four status values and what each implies for the next action. Combined with the provider/inbox prerequisites, an agent has everything needed to call it and interpret the result.

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 100% schema description coverage, the schema already documents all four parameters including the Facebook inbox_id rule and the account_id disambiguation. The description only marginally extends this (nicknames as name inputs, the admonition not to use a name as chat_id/user_id), so the baseline of 3 is appropriate.

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 ('turn a person's name... into the exact recipient') and enumerates the four providers it covers. It explicitly routes LinkedIn cases to linkedin_resolve_person + linkedin_start_conversation, so sibling disambiguation is handled in the description itself.

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

Usage Guidelines5/5

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

Supplies concrete trigger utterances ('send a WhatsApp to Julien', 'reply to Marie on Instagram'), the sequencing rule (use BEFORE sending), and an explicit negative constraint ('Never pass a name as chat_id or user_id'). It also prescribes behavior per outcome (ask when ambiguous, don't auto-send when incomplete), which is exactly the when/when-not guidance an agent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.