Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get one contact

get_contact
Read-onlyIdempotent

Fetch one WhatsApp contact: name, phone number and activity timestamps.

first_messaged_at is when a message from this number first reached them on WhatsApp, and last_interaction_at is the last message that passed in EITHER direction, so it moves when they write to you as well. A message that failed before reaching WhatsApp moves neither.

refresh shows the last refresh_contact you asked for: when it was requested, when it finished, and its outcome (updated, unchanged, number_not_connected or unavailable). While completed_at is null it is still running.

The id must belong to the number named by number_alias. An id from a different number returns not found even though the person exists.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYesContact id (`ct_…`), from `list_contacts`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: timestamp semantics, failed-message behavior, refresh outcome values, and the not-found behavior for cross-number ids.

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?

The description is front-loaded with the core action and then uses short paragraphs to explain timestamp semantics, refresh status, and the cross-number id constraint. Every sentence adds useful information without repetition.

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?

Given the rich annotations, full schema coverage, and an output schema, the description supplies everything needed to call the tool correctly. It explains the one-contact scope, key field meanings, refresh status behavior, and the critical number_alias/contact_id relationship.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters, setting a baseline of 3. The description adds a meaningful constraint not obvious from the schema: the contact_id must belong to the number_alias, otherwise the result is not found.

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: 'Fetch one WhatsApp contact', and names the returned fields: name, phone number, and activity timestamps. It distinguishes a single-contact fetch from list-style operations by emphasizing 'one', though it does not explicitly name list_contacts as the alternative.

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?

It provides an important usage constraint: the contact id must belong to the number named by number_alias, and mismatched ids return not found. However, it does not explicitly say when to use this tool versus list_contacts or refresh_contact, leaving alternatives mostly implicit.

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.