Skip to main content
Glama

henry_analyze_pair

Compare application and module files for static compatibility across EXE+DLL, APK+Kotlin, and APK+native library pairs, returning evidence-backed findings without executing files.

Instructions

Compare an application file with a module file for static compatibility.

Supported pairs:

  • EXE + DLL (Windows PE)

  • APK + Kotlin source (.kt)

  • APK + native library (PE)

The result is an evidence-backed inference, not a runtime guarantee. No files are loaded or executed.

Args: app_path: Path to the application file (EXE or APK). module_path: Path to the module file (DLL or Kotlin source). 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": {
      "app_path": "<app_path>",
      "module_path": "<module_path>"
    },
    "name": "henry_analyze_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
app_pathYes
module_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that no files are loaded or executed and that output is an evidence-backed inference rather than a runtime guarantee, and it reveals pagination via findings. It does not cover cost/runtime, error behavior on unsupported pairs, or permission needs.

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 one-line purpose, then a scannable supported-pairs list, then a critical caveat, then a compact Args block. No filler sentences; every line contributes.

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?

An output schema exists, so return values need not be explained, and the description covers inputs, accepted pair types, and safety semantics. The only real gap is what happens with an unsupported or mismatched pair (error vs empty result) and any size/time limits.

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 coverage is 0%, so the Args block is doing necessary work: it defines both path parameters and clarifies that limit/offset operate on the count of findings, plus repeats defaults. It does not specify accepted path forms (absolute vs relative) or behavior when limit is exceeded.

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 both resources ('Compare an application file with a module file for static compatibility') and then enumerates the exact pair types accepted, so an agent knows precisely what this tool does and how it differs from explain_finding or inspect_file. Scope is unambiguous.

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?

The supported-pairs list effectively tells the agent when this tool applies and implicitly when it does not (anything outside EXE+DLL, APK+kt, APK+PE). It also sets expectations that results are inferences. It stops short of explicitly naming an alternative tool or stating prerequisites for the files.

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