Skip to main content
Glama
Sign In
ih8sn1ff

ih8sn1ff

by ih8w1nd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rebuild_imports

Rebuild a dumped PE's import directory and IAT using module metadata from dump_meta.json to repair imports for analysis or execution.

Instructions

Rebuild a dump's IAT/import directory from dump_meta.json module metadata.

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": {
      "dump_path": "<dump_path>",
      "out": "<out>",
      "dump_meta": "<dump_meta>"
    },
    "name": "rebuild_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
outYes
dump_metaYes
dump_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It does not say whether the dump file is modified in place or a new artifact is written to 'out', whether existing imports are overwritten, or what permissions/inputs must be valid — all critical for a mutation tool.

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?

A single tight sentence with zero filler, front-loading the action and the artifact. Being one sentence, it is efficient but arguably under-specified rather than optimally concise.

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?

With no annotations, no output schema, and three required parameters at 0% schema coverage, the description is far too thin for an agent to invoke this correctly. It should specify the in-place vs. output-file behavior and the format of each path argument.

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%, so the description must compensate for all three parameters. It only clarifies that dump_meta is JSON module metadata; dump_path and out are left entirely undefined (input dump vs. output artifact path is guessed, not stated).

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?

States a specific verb (Rebuild) and resource (a dump's IAT/import directory) plus the source of truth (dump_meta.json module metadata). It is clear what the tool produces, though it never distinguishes itself from the related sibling rebuild_pe, which an agent would plausibly confuse it with.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The name implies it is used after a dump exists, but nothing states prerequisites or when rebuild_pe would be preferred instead.

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