Skip to main content
Glama

henry_inspect_file

Statically inspect one file to return a structured report of its type, format, and key properties, covering PE, APK, and Kotlin source metadata.

Instructions

Inspect a single file statically and return a structured report.

Use this first to understand a file's type, format, and key properties before comparing it with another file.

Supported formats:

  • Windows PE (EXE / DLL): architecture, imports, exports, dependencies

  • Android APK: package, SDK, permissions, native libraries, DEX files

  • Kotlin source (.kt): package, imports, classes, functions

Args: path: Absolute or relative path to the file to inspect. limit: Maximum number of findings to return (default 1000). offset: Number of findings to skip (default 0).

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": {
      "path": "<path>"
    },
    "name": "henry_inspect_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden, and it delivers key traits: analysis is "static" (the artifact is not executed), the output is a structured report, and results are paginated via limit/offset. It does not address permissions, cost, or whether findings are exhaustive versus capped, which keeps it out of the top band.

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?

Front-loaded purpose sentence, then a compact supported-format list that tells the agent whether the tool applies, then a short Args block. Every element maps to a decision the caller must make; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All three parameters are explained, supported formats are enumerated, and an output schema exists so return structure need not be described. For a read-only single-file inspector this is everything an agent needs to select and invoke it correctly.

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?

Schema description coverage is 0%, so the description must define all three parameters, and it does: path as absolute or relative, limit as maximum findings (default 1000), and offset as findings to skip (default 0). It usefully establishes that "findings" are the paginated unit, though it does not describe how findings are ordered.

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?

States a specific verb and resource ("Inspect a single file statically and return a structured report") and immediately enumerates the exact artifact types handled: PE, APK, and Kotlin source. It also distinguishes itself from pair-based analysis by saying to run it "first ... before comparing it with another file."

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?

"Use this first to understand a file's type, format, and key properties before comparing it with another file" gives a clear ordering rule relative to pair comparison. It does not name the counterpart tool explicitly or state any when-not-to-use conditions, so it falls short of full routing guidance.

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