Skip to main content
Glama
hail

hail

Official

Look up a contact

lookup_contact
Read-onlyIdempotent

Find workspace contacts by name, email, or phone fragment and return up to ten matches with names, phone numbers, emails, and IDs.

Instructions

Find workspace contacts by name, email or phone fragment.

Returns up to ten matches containing names, phone numbers, email addresses and IDs. Several matches can refer to different people.

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

Input Schema

NameRequiredDescriptionDefault
queryYesPart of a name, email address or phone number, such as ``Dana``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.32.0
    • addedInput schema / properties / query / description
      Added value: +"Part of a name, email address or phone number, such as ``Dana``."
  2. First observedv0.29.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. Beyond that the description adds genuinely useful behavior: a hard cap of ten matches and the warning that several matches may refer to different people, which signals ambiguity resolution is the caller's responsibility. It stops short of describing match ranking or partial-match semantics.

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?

Two short sentences, front-loaded with the verb and searchable fields, followed by result expectations. No wasted wording, though the second sentence could be tightened and the ambiguous indentation adds no structure.

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?

This is a one-parameter read tool with a full annotation set and an output schema, so return-value detail is not required. The description covers search scope, result cap, and ambiguity risk — everything an agent needs to call it correctly and interpret the response.

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% and the single parameter already documents itself as 'Part of a name, email address or phone number' with an example. The description's 'fragment' phrasing reinforces partial-match intent but adds little beyond the schema text, so the baseline of 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 ('Find') and resource ('workspace contacts') plus the three searchable fields (name, email, phone fragment), which is far clearer than the title alone. It does not explicitly contrast itself with the sibling list_contacts, so an agent must infer the distinction between searching and listing.

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 rather than stated: the fragment-based wording suggests 'use when you have a partial identifier,' but there is no explicit when-to-use, no exclusion, and no pointer to list_contacts for full enumeration. The agent is left to infer the boundary from the sibling name.

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