Skip to main content
Glama

graph_get_manager

Retrieves a user's manager from the organization directory, or your own manager when no user ID is given. Use it to find who someone reports to.

Instructions

Get a user's manager from the organization directory.

Reading someone else's manager requires the User.Read.All permission.

Args: user_id: User ID or email address. Empty targets the signed-in user.

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

Input Schema

NameRequiredDescriptionDefault
user_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real value by disclosing the permission requirement for cross-user reads and the default self-targeting behavior. It does not cover edge cases such as a user with no manager or a nonexistent identifier, nor what the response contains.

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?

Three short, front-loaded lines: the action first, then the permission caveat, then the argument meaning. No filler or redundant restatement of the tool name.

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 one-optional-parameter lookup with no output schema and no annotations, the definition covers action, permission gating, and parameter defaults adequately. A brief note on what is returned or on missing-manager behavior would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: user_id accepts a user ID or email address, and an empty value targets the signed-in user — semantics the bare string schema does not express. Only the accepted ID formats beyond email are left unspecified.

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?

States a specific verb and resource: 'Get a user's manager from the organization directory,' which is distinct from sibling read tools like graph_get_profile or graph_get_team. No explicit sibling differentiation is offered, but the resource ('manager') is specific enough that an agent can tell what it retrieves.

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?

Implicitly conveys usage by explaining that an empty user_id targets the signed-in user and that reading someone else's manager needs User.Read.All. There is no explicit when-to-use/when-not-to-use framing, but for a narrow single-purpose lookup there is little alternative confusion to resolve.

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

Deploy Server

Other Tools