Skip to main content
Glama
Sign In
Microsoft Active Directory MCP Server

Microsoft Active Directory MCP Server

by nks1097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ad_get_computer

Retrieve details for a specified Active Directory computer by identity, enabling inspection of its directory attributes and configuration.

Instructions

[Computers & Devices] [READ] Consultar detalhes de um computador.

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": {
      "identity": "<identity>"
    },
    "name": "ad_get_computer"
  }
}

Input Schema

NameRequiredDescriptionDefault
identityYes
correlation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 burden; it only conveys read-only intent via the '[READ]' tag. It says nothing about permissions required, behavior when the identity does not resolve (error vs empty), or whether the lookup is scoped to a domain that must be configured first.

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?

One short sentence with the category and read-only tag front-loaded, so the functional part is easy to find. Nothing is wasted, though the description is under-specified rather than dense.

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?

An output schema exists, so return values need not be described. However, for a lookup tool whose only job is resolving an identifier, the missing input format and the missing distinction from the list/search siblings leave an agent without what it needs to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, and the description adds nothing: 'identity' is left ambiguous (distinguished name? sAMAccountName? GUID?) even though that ambiguity will directly cause failed calls. 'correlation_id' is likewise unexplained, presumably a tracing id.

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 states a specific verb and resource: retrieve the details of a single computer object, and the [Computers & Devices] tag places it in the right domain. It does not differentiate from close siblings such as ad_list_computers, ad_search_computers, or ad_get_stale_computers, so an agent must infer that 'a computer' means single-object lookup by identifier.

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 guidance on when to use this versus ad_search_computers or ad_list_computers, and no precondition stated for the required identity parameter. The catalog offers many computer-related tools, so the absence of routing cues is a real gap.

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