Skip to main content
Glama

search_contacts

Read-onlyIdempotent

Search Google Contacts by name, email, phone, organization, or notes and return paginated matches for contact lookup.

Instructions

Search Google Contacts by name, email address, phone number, organization, or notes.

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
queryYesSearch query (name, email, phone, company, etc.)
pageSizeNoMaximum number of results to return (1-30, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds the set of searchable fields, which is genuinely useful context, but says nothing about result ordering, partial matching, or what happens when no matches are found.

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?

A single front-loaded sentence with no filler, and the verb and resource come first. It is slightly under-structured in that the field list is run together rather than separated from any behavioral guidance.

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-only search with full schema coverage and rich annotations, the description covers the essential 'what' and the searchable surface. Remaining gaps such as match semantics and empty-result behavior are minor, and no output schema exists that would need explaining.

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 both query and pageSize are already documented in the schema, including the 1-30 range and default of 20. The description's field list overlaps with the query parameter's own description ('name, email, phone, company, etc.') rather than adding new meaning, so 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?

States a specific verb and resource ('Search Google Contacts') and enumerates the searchable facets (name, email, phone, organization, notes). It is distinguishable from sibling list_contacts only by inference from the word 'Search', not by an explicit contrast.

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?

The description implies usage (use this to find contacts by any of several fields) but gives no explicit when-to-use or when-not-to-use guidance. It never mentions list_contacts for browsing or get_contact for fetching a single record, leaving the agent to infer the choice from sibling names alone.

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