Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

directory

Retrieve user profiles, managers, direct reports, and presence, or search users by email or ID to resolve people and organizational details.

Instructions

User directory: profiles, managers, direct reports, presence, and user search

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": {
      "operation": "<operation>"
    },
    "name": "directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoUser email address
queryNoSearch query (for search_users)
userIdNoUser ID (or "me" for current user)
operationYesOperation to perform
maxResultsNoMax results (default: 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the topic list: no indication of required permissions, whether absence of a manager or presence yields an error or empty result, whether presence is real-time, or what the response shape looks like. The only behavioral inference available is that these are read-style lookups, which comes from the nouns rather than any explicit statement.

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?

A single short sentence, front-loaded and free of filler, which is appropriate for a topic statement. It is efficient, though its terseness is partly under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool bundles six distinct operations with five parameters and ships no output schema and no annotations, so the description should explain how operations map to inputs and what each returns. Instead it only lists topics, leaving the agent to reverse-engineer behavior from the enum and param names alone. That is thin for a multi-operation directory tool.

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%, including an operation enum that names each lookup, so the schema already does the parameter work and a baseline 3 applies. The description's mention of 'presence' and 'user search' loosely maps to the get_presence and search_users operations, but it adds no detail on which parameter each operation requires (email vs userId vs query) beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the resources covered (profiles, managers, direct reports, presence, user search), which matches the operation enum and hints at the tool's scope. However, it is a bare noun phrase with no verb like 'look up' or 'retrieve', so the agent must infer that this is a read-oriented user lookup tool rather than, for example, a directory administration tool. It distinguishes itself somewhat from siblings like contacts or groups, but only through the word 'user'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of when another tool (e.g. contacts, groups, search) is the better choice, and no statement of prerequisites or limitations. The agent must decide entirely on its own that this is the tool for org-directory lookups rather than cross-account search or contact lookup.

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