Skip to main content
Glama

Relaties zoeken

find_contacts
Read-only

Search existing customers by partial name or email, or list all contacts when no query is given, to check before creating a new contact and avoid duplicates.

Instructions

Find customers by part of their name or e-mail address. Without a query it lists all of them. Check here before creating a new contact.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=false, so the safety profile is covered; the description adds real behavior beyond them: substring matching on name or e-mail, and that omitting the query returns the full list. It does not mention result caps, sorting, or pagination, which matters for a list-everything mode.

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?

Three short sentences, front-loaded with the primary capability, then the empty-argument behavior, then the recommended call moment. No filler or restatement of the name.

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?

A one-parameter read tool with rich annotations and no output schema does not need much, and the description covers purpose, matching, empty-query behavior, and usage timing. The remaining gap is what a large unfiltered result set looks like (limits/ordering).

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 description coverage is 0%, so the description must carry the single parameter's meaning — and it does, defining query as a partial name or e-mail match and clarifying that it is optional. Case-sensitivity and format expectations are left unstated.

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 customers by part of their name or e-mail address" gives a specific verb, resource, and matching strategy, and the closing sentence signals the counterpart write tool (creating a contact). An agent can distinguish this read/search tool from save_contact without inspecting 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?

It states a concrete call context ("Check here before creating a new contact") and explains the no-argument case ("Without a query it lists all of them"), so both the dedup-check and full-listing usages are discoverable. It stops short of naming the alternative sibling explicitly or saying when not to use this tool.

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