Skip to main content
Glama

collection_info

Query BloodHound Enterprise collection infrastructure status: retrieve manifests, collectors, clients, jobs, tasks, and events. Use info_type to select specific details like checksums, logs, or client info.

Instructions

Query BloodHound Enterprise collection infrastructure status.

info_type options:
    collector_manifest - get collector manifest (needs: collector_type)
    collector_checksum - get collector checksum (needs: collector_type, release_tag)
    kennel_manifest - get kennel manifest
    kennel_enterprise_manifest - get kennel enterprise manifest
    clients - list clients
    client - get a client (needs: client_id)
    client_completed_tasks - list completed tasks for a client (needs: client_id)
    client_completed_jobs - list completed jobs for a client (needs: client_id)
    jobs_available - list available jobs
    jobs_finished - list finished jobs
    jobs - list jobs
    job_current - get current job
    job - get a job (needs: job_id)
    job_log - get job log (needs: job_id)
    tasks_available - list available tasks
    tasks_finished - list finished tasks
    tasks - list tasks
    task_current - get current task
    task - get a task (needs: task_id)
    task_log - get task log (needs: task_id)
    events - list scheduled events
    event - get scheduled event (needs: event_id)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNo
limitNo
job_idNo
task_idNo
event_idNo
client_idNo
info_typeNoclients
asset_nameNo
release_tagNo
collector_typeNo
Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly states 'Query' (read-only) and details all operations and their parameter dependencies. It does not discuss authorization, rate limits, or error behavior, but for a status query tool, the disclosed information is substantial and accurate.

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 front-loaded with its purpose and then organized as a clean list of options with dependencies. Every line earns its place; the length is justified by the number of sub-operations. No filler or redundancy.

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?

Given the complexity (10 parameters, many info_type variants), the description covers all operation-specific requirements. It does not describe return values or error handling, but with no output schema and the read-only nature, the provided information is largely sufficient for an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, so the description must compensate. It does so admirably by listing each info_type and explicitly stating which parameters are required for each, effectively providing a full usage map. This adds critical meaning 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 opens with a clear, specific verb+resource statement: 'Query BloodHound Enterprise collection infrastructure status.' It then enumerates all info_type options, which precisely distinguishes this from sibling tools like user_info or domain_info. The scope is unambiguous.

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 an extensive list of info_type values with their required parameters, giving clear context on when to use each subtype. It does not explicitly mention alternatives or when not to use the tool, but the sibling tool names and the focused scope make the intended usage obvious.

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/err0n-0x2A/bhe_mcp'

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