Skip to main content
Glama

Search people

search_people
Read-only

Look up people by name or email in the organization directory or personal contacts. Use it to find someone's email address before sending mail.

Instructions

Find people by name or email address in the organization directory (global address list) and/or personal contacts. Useful for looking up someone's email address before sending.

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_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 10)
queryYesName, partial name or email address
sourceNoWhere to search (default "all")

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, correctly telling the agent this is a safe, closed-domain read. The description adds that searches can span both the global address list and personal contacts, but it says nothing about result ordering, truncation behavior, or matching semantics (exact vs partial), leaving real behavioral gaps for a search tool.

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?

Two short sentences, front-loaded with the core verb and resource, with no filler. The final clause does useful work by naming the email-lookup scenario, though it is slightly redundant with the first sentence's mention of email addresses.

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 simple three-parameter read-only lookup with full schema coverage and no output schema, the definition covers what is needed to select and invoke the tool. The main omission is a hint about what a result contains (name, email, source) and how limit interacts with matching, but this is minor at this complexity level.

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 query, limit, and source are all documented in the schema with defaults and an enum. The description's wording ("by name or email address") mirrors the query description rather than adding new meaning, so the 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?

The description names a specific verb ("Find") and resource ("people by name or email address") with clear scope: the organization directory/global address list and/or personal contacts. That distinguishes it from contact-mutation siblings such as create_contact or delete_contact, though it never explicitly contrasts with list_contacts or get_contact.

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 second sentence gives a concrete usage context ("looking up someone's email address before sending"), which implies a when-to-use scenario. However, it offers no exclusions or explicit alternative routing, e.g. when to prefer list_contacts for browsing versus this search for a known name or address.

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