Skip to main content
Glama

Hail Communication for AI

Look up a contact

lookup_contact
Read-onlyIdempotent

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``.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of ten results and the warning that several matches can refer to different people, which steers the agent toward disambiguation rather than assuming a single hit. It stops short of stating match ordering or whether matching is substring or prefix.

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?

Two short sentences with zero filler. The core capability is front-loaded in the first sentence and the result contract plus the ambiguity caveat follow in the second, which is the right order for an agent deciding whether to call.

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 two-parameter read tool with full schema coverage, an output schema, and complete annotation coverage, this covers what the agent needs: what to search on, the ten-result ceiling, and the risk of multiple distinct people. Only minor gaps remain, such as ordering of matches and behavior on no results.

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%, so the schema already documents both parameters including the 'part of a name, email address or phone number' semantics. The description's phrase 'name, email or phone fragment' largely restates the schema, adding only the word 'fragment' to reinforce partial matching. Baseline 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 leads with a specific verb and resource ('Find workspace contacts') and names the three searchable fields (name, email, phone fragment). It is clearly a search tool, which implicitly separates it from list_contacts, but it never explicitly contrasts the two, so sibling differentiation is left to inference.

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: an agent can infer this is for fuzzy contact lookup when it has a partial identifier. There is no explicit guidance on when to prefer list_contacts or create_contact, and no note about what to do when zero matches are returned.

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.

Resources