Skip to main content
Glama

search_contacts

Read-only

Find contacts by name, organization, email, or phone number. All query words must match; returns matching names, organizations, emails, and phone numbers.

Instructions

Find contacts. The query matches name, organization and email (any case), and phone numbers when the query looks like a phone number. All words of the query must match. Returns name, organization, emails and phones. Use get_contact for the full card. Notes are never returned.

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": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost results to return. Default 25, maximum 200.
queryYesName, organization, email or phone number to look for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say read-only and closed-world; the description adds substantive behavior an agent cannot infer from them: case-insensitive matching across three fields, phone-number matching triggered by query shape, the all-words-must-match rule, the returned field set, and that notes are excluded. These are exactly the traits that determine whether a query will succeed.

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?

Four short sentences, front-loaded with the purpose and matching rules before the return fields and the diversion to get_contact. Every sentence carries information that changes agent behavior; nothing is filler.

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?

With no output schema, the description compensates by naming the returned fields (name, organization, emails, phones) and the notable exclusion (notes). Combined with a fully documented schema and read-only annotations, an agent has everything needed to call it and interpret the result correctly.

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 coverage is 100%, so the baseline is 3, but the description genuinely enriches the query parameter by describing case handling, conjunctive word matching, and the phone-number heuristic that the schema's "Name, organization, email or phone number to look for" does not convey. The limit parameter is left entirely to the schema, which already documents default and maximum.

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?

"Find contacts" is a specific verb plus resource, immediately followed by the matching scope (name, organization, email, phone). It explicitly names the sibling get_contact as the full-record alternative, so an agent can distinguish the two without reading either schema.

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?

The description routes the agent: use this for finding, use get_contact for the full card, and notes are never returned (implying search_notes for note content). It gives clear context but stops short of stating explicit exclusions such as when the query is better served by another search tool.

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