Skip to main content
Glama

Get one employee profile

directory_get_employee
Read-onlyIdempotent

Retrieves a full employee profile by ID or email, including manager, direct reports, phone, and skills; salary band appears only for admin role.

Instructions

Full profile for one employee by id or email (give one of them): manager, direct reports, phone, skills. Salary band is included only for the admin role. 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_get_employee"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEmployee id, e.g. E004
emailNo

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
teamNo
emailYes
phoneNo
titleNo
skillsNo
managerNo
locationNo
departmentNo
start_dateNo
salary_bandNo
direct_reportsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, idempotent read. The description adds materially useful behavior: role requirements and field-level salary visibility limited to admins. It does not cover not-found or unauthorized behavior, but the annotations and output schema reduce the remaining burden.

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?

Three short sentences front-load the purpose, lookup method, and access constraints. The field enumeration is compact, though slightly redundant with the output schema.

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 two-parameter read lookup with annotations and an output schema, the definition supplies the essential role and visibility constraints plus the either/or identifier rule. Minor ambiguity remains around missing identifiers and error behavior, but the definition is broadly complete.

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?

The description adds important choice semantics by saying to give one of id or email. However, with only 50% schema description coverage, it does not clarify email matching behavior or what occurs if both identifiers are supplied.

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?

Identifies a specific read operation: returning a full employee profile by known id or email. It clearly separates this as a single-record lookup, though it does not explicitly contrast itself with search/list siblings.

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?

Gives useful preconditions: provide one of id or email and require the viewer role. It does not explicitly say when to use this rather than a directory search, nor what happens if both or neither identifier are supplied.

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