Skip to main content
Glama
Sign In
BloodHound MCP

BloodHound MCP

by stevenyu113228
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_all_enabled_users_never_logged_in

Identify enabled Active Directory users who have never logged in to detect potential security risks and unused accounts.

Instructions

List all enabled user(s) but never logged in

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": {
      "domain": "<domain>"
    },
    "name": "list_all_enabled_users_never_logged_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 full burden. It mentions 'enabled' and 'never logged in' but doesn't clarify behavioral aspects like whether this is a read-only operation, what permissions are required, how results are formatted, or if there are rate limits. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is extremely concise with a single, clear sentence. It's front-loaded with the core purpose and wastes no words, making it easy to parse quickly.

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?

Given no annotations, 0% schema coverage, no output schema, and a parameter-heavy context (1 required param), the description is incomplete. It states what the tool does but omits critical details about parameters, behavior, and output, leaving the agent under-informed for effective use.

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%, and the description provides no information about the single required parameter 'domain'. It doesn't explain what 'domain' refers to (e.g., Active Directory domain, Azure tenant), its format, or examples. The description fails to compensate for the lack of schema documentation.

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 clearly states the verb ('List') and resource ('all enabled user(s) but never logged in'), making the purpose understandable. It distinguishes from many siblings by focusing on login status, though it doesn't explicitly differentiate from similar tools like 'list_enabled_users' or 'list_all_enabled_users_logged_in_last_90_days'.

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?

No guidance is provided on when to use this tool versus alternatives. Given the many sibling tools with overlapping scopes (e.g., 'list_enabled_users', 'list_all_enabled_users_logged_in_last_90_days'), the description offers no context for selection, leaving the agent to infer based on names alone.

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