Skip to main content
Glama
mwnickerson

BloodHound MCP Server

by mwnickerson

search_objects

Find Active Directory and Azure objects in BloodHound by name or ID. Search with partial names, filter by type, and manage results with pagination.

Instructions

Search for objects in the BloodHound database by name or Object ID.
This is useful for finding specific objects when you don't know their exact ID.

Args:
    query: Search text - can be a partial name, full name, or Object ID
    object_type: Optional filter by object type:
        - For Active Directory: User, Computer, Group, GPO, OU, Domain
        - For Azure: AZUser, AZGroup, AZDevice, etc.
    limit: Maximum number of results to return (default: 100)
    skip: Number of results to skip for pagination (default: 0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
object_typeNo
limitNo
skipNo
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the search functionality and pagination behavior (default values for limit/skip), but doesn't mention performance characteristics, rate limits, authentication requirements, or what happens with invalid queries. It provides basic operational context but lacks deeper behavioral insights.

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 perfectly structured with a clear purpose statement followed by well-organized parameter documentation. Every sentence earns its place, with no redundant information. The bullet-point format for object_type values enhances readability without wasting space.

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 search tool with 4 parameters and no annotations/output schema, the description provides excellent parameter documentation and clear purpose. However, it doesn't describe the return format (what fields objects have, structure of results) or error conditions, which would be helpful given the lack of output schema.

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

Parameters5/5

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

Despite 0% schema description coverage, the description provides comprehensive parameter documentation that fully compensates. It explains each parameter's purpose, provides examples for 'query' and 'object_type', lists valid values for object_type, and specifies default values for limit and skip. This adds significant value beyond the bare schema.

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

Purpose5/5

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

The description clearly states the tool's purpose with specific verbs ('search for objects') and resources ('BloodHound database'), and distinguishes it from siblings by focusing on name/ID-based searching rather than relationship analysis or specific object type queries. The opening sentence provides a complete functional statement.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('when you don't know their exact ID'), but doesn't explicitly mention when not to use it or name specific alternatives among the many sibling tools. The guidance is helpful but could be more comprehensive regarding tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mwnickerson/bloodhound_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server