Skip to main content
Glama

Search contacts

contacts_search
Read-onlyIdempotent

Finds contacts by exact email, status or tag, newest first. Free and read only. Status "subscribed" means active; "unsubscribed" covers suppressed addresses. Returns at most limit rows (default 50, max 200). Requires API key scope: read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contacts_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly contacts that carry this tag.
emailNoExact email address to look up.
limitNoHow many rows to return (1 to 200, default 50).
statusNoFilter by status. subscribed = active, unsubscribed = suppressed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still adds genuinely new behavioral facts: result ordering (newest first), the result-cap behavior with default 50 and max 200, and an auth requirement (API key scope: read).

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?

Four short sentences, front-loaded with the verb and filters, then behavior, then limits, then auth — good ordering with no filler. Minor redundancy: the status equivalence (subscribed = active, unsubscribed = suppressed) and the limit default repeat what the schema descriptions already state.

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 four-optional-parameter search with strong annotations, the definition covers scope, ordering, result caps, and auth. The remaining gap is the shape of returned rows (no output schema exists), which would help an agent know what fields to expect from a match.

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 all four parameters, including the status enum meanings and the limit bounds. The description's additions — "exact" matching for email and an implicit sort order that has no corresponding parameter — are modest, 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 ("Finds contacts") plus the three filterable fields and the ordering ("newest first"). The "read only" framing also implicitly separates it from the write sibling contacts_add, though no sibling is named explicitly.

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 by naming the filter dimensions and stressing "exact email" (i.e., not a fuzzy/partial search), which is a real selection constraint. However, it does not say when to prefer this over another lookup path, whether filters combine with AND semantics, what happens with zero filters, or what to do when the exact email is unknown.

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