Timbre

Overview Schema Source Related Servers Discussions Admin

find_contact

Read-only

Locate a person by name, address, or phone number across Contacts and Mail, returning their addresses, numbers, message count, and last exchange.

Instructions

Find a person by name, address or phone number, in the user's Contacts and in their mail: each one's addresses, numbers, how many messages they exchanged with the user and when last.

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

Input Schema

Name	Required	Description	Default
`limit`	No	At most this many (default 10, max 25).
`query`	Yes	A name, an address or part of one, or a phone number.

Output Schema

Name	Required	Description	Default
`contacts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.2Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real context beyond them: the lookup spans two data sources and returns per-person addresses, numbers, exchanged-message counts, and last-contact timing, which tells the agent this is an aggregating lookup rather than a plain directory hit.

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?

It is a single front-loaded sentence with no filler, and the searchable fields come before the return-shape clause. The colon-appended list of returned attributes is slightly dense and run-on, which keeps it from being a clean 5.

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?

For a two-parameter read-only lookup with full schema coverage and an output schema, the description covers what the tool searches, where it searches, and what kind of result comes back. Nothing an agent needs in order to invoke it correctly is missing.

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 parameters are already documented, making 3 the baseline. The description's phrase 'by name, address or phone number' mirrors the query parameter's schema text without adding syntax, format, or matching-behavior details, and the limit parameter is not mentioned at all.

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 names a specific verb (find) and resource (a person) and scopes the search to two corpora — the user's Contacts and their mail — which separates it from message-oriented siblings like search_mail. It stops short of naming any sibling tool or explicitly stating what it is not, so it is clear but not fully differentiated.

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 only implied: an agent can infer you call this when you want to locate a person rather than a message. There is no explicit when-to-use statement, no when-not-to-use condition, and no pointer to alternatives such as search_mail for message-level lookup.

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