Skip to main content
Glama

Inspect Native Load Image

inspect_native_load_image
Idempotent

Verifies a loaded DOS MZ or selected COM image against an immutable snapshot, returning digest, mapping, relocation, and mismatch-coordinate observations without executing or modifying the target.

Instructions

Verify the provider's loaded DOS MZ or explicitly selected COM image against its immutable target snapshot: complete original/modified source-byte digests, header/module file mappings and memory digests, relocations and external entry. Returns measured observations and independent checks with mismatch coordinates. COM verification includes its imposed entry register context and does not claim PSP/runtime coverage. Overlay and uninitialized coverage remain explicit; other formats return unsupported. Does not execute or modify the target.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_native_load_image"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: what is compared, that mismatches come with coordinates, the explicit coverage boundaries (overlay, uninitialized, PSP/runtime), and the non-goal of executing or modifying the target. However, it asserts 'does not execute or modify the target' while readOnlyHint=false, leaving a mild unresolved tension about side effects such as attaching to or snapshotting the provider; that ambiguity is not addressed.

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?

Three sentences, front-loaded with the primary action and comparison target, then scope limits, then the non-execution guarantee. Dense jargon but almost no filler; each clause carries distinct information about coverage or output.

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?

This is a complex verification tool with zero parameters, no output schema, and no guidance on how the immutable target snapshot is established or how a COM image is 'selected' — the agent cannot tell what precondition makes a call meaningful. Return values are described only in headline terms (observations, checks, mismatch coordinates) with no output schema to fall back on, leaving the contract underspecified for the tool's complexity.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The phrase 'explicitly selected COM image' implies a selection input that the empty schema does not expose, which is a small unexplained gap but not a parameter-semantics failure.

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?

Names a specific verb and resource: verify a loaded DOS MZ or explicitly selected COM image against its immutable target snapshot, with named outputs (source-byte digests, file mappings, relocations, external entry). An agent can tell this is a load-image integrity comparison rather than the sibling inspect_native_api/instruction/data_type tools, though the distinction is carried mostly by domain vocabulary rather than an explicit contrast.

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?

Applicability is implied by format: works on DOS MZ or an explicitly selected COM image, and 'other formats return unsupported' tells the agent when it will not work. There is no explicit when-to-use versus when-not guidance, no prerequisites, and no routing to an alternative for non-MZ/COM binaries.

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