Skip to main content
Glama
binalyze

Binalyze AIR MCP Server

Official
by binalyze

assign_image_acquisition_task

Assign disk image acquisition tasks to specific endpoints and volumes for digital forensics and incident response investigations.

Instructions

Assign a disk image acquisition task to specific endpoints and volumes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdNoThe case ID to associate the acquisition with (optional)
repositoryIdYesThe repository ID where the image will be saved
endpointsYesArray of endpoints and volumes to image (e.g., [{"endpointId": "uuid", "volumes": ["/dev/sda1"]}]). At least one endpoint and one volume per endpoint required.
organizationIdsNoArray of organization IDs. Defaults to [0]
bandwidthLimitNoBandwidth limit in KB/s. Defaults to 100000
enableCompressionNoWhether to enable compression. Defaults to true
enableEncryptionNoWhether to enable encryption. Defaults to false
encryptionPasswordNoPassword for encryption if enabled
chunkSizeNoChunk size in bytes. Defaults to 1048576
chunkCountNoNumber of chunks to acquire. Defaults to 0 (acquire until end).
startOffsetNoOffset in bytes to start acquisition from. Defaults to 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 'assign' but doesn't disclose behavioral traits such as permissions required, whether this is a destructive operation (e.g., imaging might affect system state), rate limits, or what happens after assignment (e.g., task status, notifications). This leaves significant gaps for a tool with potential system impact.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It directly communicates the tool's function, making it easy to parse and understand 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 the complexity (11 parameters, no annotations, no output schema), the description is incomplete. It doesn't address behavioral aspects, usage context, or output expectations (e.g., what is returned after assignment). For a tool that likely involves system operations and multiple parameters, more context is needed to guide the agent effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all 11 parameters. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., how 'enableEncryption' interacts with 'encryptionPassword') or providing examples. Baseline is 3 as the schema handles parameter documentation adequately.

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 action ('Assign') and target ('disk image acquisition task to specific endpoints and volumes'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'assign_acquisition_task' or 'acquire_baseline', which appear related but have different scopes or methods.

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. With siblings like 'assign_acquisition_task' and 'acquire_baseline' present, the description lacks context on prerequisites, exclusions, or comparative use cases, leaving the agent to infer usage.

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/binalyze/air-mcp'

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