Skip to main content
Glama
huaidj-rufus

huaidj-rufus

by huaidj

inspect_disk_image

Read-onlyIdempotent

Hash a local ISO/IMG and inspect boot-image signatures without modifying the image or USB, optionally verifying it against an expected SHA-256.

Instructions

Hash a selected local ISO/IMG and inspect boot-image signatures without changing the image or any USB.

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": {
      "image": "<image>"
    },
    "name": "inspect_disk_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesConfigured image alias or local .iso/.img path within configured image roots.
expected_sha256NoExpected SHA-256 obtained from a trusted publisher or an explicitly selected local image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered by structured data and the 'without changing the image or any USB' clause largely restates it. The description does add the useful behavioral fact that the tool computes a hash and checks boot signatures, but it says nothing about what happens on a hash mismatch or what the inspection produces.

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?

A single sentence with zero filler, with the action front-loaded and the non-mutation guarantee placed at the end where it reads as a constraint. Nothing could be removed without losing information.

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 two-parameter read-only tool with a fully documented schema and no output schema, the description covers what the tool does and what it will not modify. The only shortfall is that 'inspect boot-image signatures' leaves the nature of the result (pass/fail, detected boot modes, signature details) undefined, which matters for an inspection tool.

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 coverage is 100% and both parameters carry their own descriptions, including the allowed alias-versus-path forms for 'image' and the trust rationale for 'expected_sha256'. The tool description adds no meaning beyond the schema, so the baseline 3 applies.

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 names two specific operations (hashing a local ISO/IMG and inspecting boot-image signatures) against a clearly scoped resource. It implicitly separates itself from USB-writing siblings by saying it touches no USB and no image, though it never names an alternative directly.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'selected local ISO/IMG' and the explicit exclusion of USB mutation, which tells an agent this is the local-file inspection path. There is no explicit statement of when to prefer this over siblings such as verify_usb_image or inspect_export_library, so the agent must infer the boundary.

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