Skip to main content
Glama

contacts_search

Read-only

Search Outlook contacts by name prefix to find matching people and read their contact details.

Instructions

Find contacts whose name starts with query.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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=true and openWorldHint=true, so safety is covered. The description adds the useful behavioral fact that matching is prefix-based on the contact name rather than substring or field-wide, but it says nothing about case sensitivity, result caps, or ordering.

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?

One short sentence with the matching rule front-loaded and no filler. It is efficient for a one-parameter tool, though the brevity borders on under-specification of edge cases rather than polished conciseness.

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 single-parameter read-only lookup with an output schema and clear annotations, the description covers enough to invoke it correctly. The remaining gap is result-set behavior (limits, ordering, empty-result handling), which is minor at this complexity.

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 0% and the single property is bare ('Query'), so the description must carry the meaning — and it does partly, by defining the argument as a name prefix. It still leaves format details (case sensitivity, whitespace handling, minimum length) unspecified, so compensation is only partial.

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 gives a specific verb (find) plus resource (contacts) and even names the match rule (name starts with `query`), so the operation is unambiguous. It does not differentiate itself from sibling searches such as mail_search or onedrive_search, though the resource name does most of that work.

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 this is the contacts-domain search because of the tool name and the 'contacts' wording. There is no explicit statement of when to prefer this over other search tools, no exclusions, and no note on what to do if prefix matching returns nothing.

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