Skip to main content
Glama

Search the employee directory

directory_search
Read-onlyIdempotent

Search employee profiles by name, title, team, skill, or location to find coworkers. Returns public fields only, with pagination and role-based access.

Instructions

Find employees by name, title, team, skill or location. Returns public profile fields only (no phone numbers). Paginated. Requires role: viewer.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax items per page (default 10, max 50)
queryNoFree text: name, title, skill, team or location. Empty lists everyone.
cursorNoOpaque cursor from a previous page (next_cursor)
locationNo
departmentNo

Output Schema

NameRequiredDescriptionDefault
totalYes
employeesYes
next_cursorYesPass as cursor to get the next page; null when done

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-redundant context: results are limited to public profile fields with phone numbers excluded, results are paginated, and a viewer role is required. It stops short of describing match semantics (AND vs OR across fields) or result ordering.

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?

Four short sentences, each carrying a distinct fact (capability, output scope, pagination, authorization), with the core capability front-loaded. There is no filler or redundancy.

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 read-only, zero-required-parameter search with an output schema and full annotations, the description covers capability, output privacy scope, pagination, and access requirements. The main remaining gap is query semantics across the five searchable dimensions, which an agent would likely need to combine filters correctly.

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 coverage is 60% and the schema already documents limit, query, and cursor with defaults and bounds. The description restates the searchable fields and adds that free text can span skill and team, which slightly enriches query meaning, but location and department remain undocumented in both schema and description, and no matching rules are given.

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?

"Find employees by name, title, team, skill or location" gives a specific verb plus resource and even enumerates the matching dimensions, so the agent knows this is a directory search rather than a record fetch. It does not explicitly contrast itself with directory_get_employee, so the sibling distinction is inferable rather than stated.

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 description implies search-style usage through "Find employees by ..." and adds the prerequisite "Requires role: viewer", which is real guidance. It never says when to prefer directory_get_employee over this search, nor when the search is the wrong choice.

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