Skip to main content
Glama
resc
by zney295

inspect_disk_headers

Reads regular disk image headers to return up to eight volume samples for read-only forensic inspection, without repair or extraction.

Instructions

Limited Python backend: read-only regular-image header evidence. No repair/extraction. Returns at most eight volume samples.

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": {
      "target_path": "<target_path>"
    },
    "name": "inspect_disk_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sector_sizeNo
target_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and discloses read-only behavior, exclusion of repair/extraction, and a return cap of eight volume samples. It omits supported image formats, error behavior, permission requirements, and what 'header evidence' actually includes, leaving meaningful gaps.

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?

The description is brief and front-loads the read-only limitation and output cap. The fragmentary style ('Limited Python backend: ...') is slightly awkward but does not waste words.

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?

For a two-parameter tool with no annotations and no output schema, the description is too thin. It does not explain parameter semantics, return structure beyond the sample count, or supported input types, leaving an agent without enough context to invoke it confidently.

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 does not mention target_path or sector_size at all. The phrase 'regular-image' hints that target_path is an image file, but the sector_size enum values (512/4096) are completely unexplained.

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

Purpose3/5

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

The description conveys that the tool inspects headers of regular disk images in a read-only way, but the phrasing 'header evidence' and 'Limited Python backend' is vague and does not state a clear verb-resource pair. It does distinguish the tool from repair/extraction, which helps an agent understand its scope.

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?

Only a negative constraint is provided: no repair or extraction. There is no guidance on when to choose this tool, what prerequisites exist, or what alternatives it might replace. An agent cannot tell whether it should use this for partition tables, filesystem headers, or another inspection task.

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