uos-mcp

Overview Schema Source Related Servers Discussions Admin

analyze_pe

Extract headers, sections, imports, exports, and version resource from a PE binary to report interface facts. Run on files inside the VM sandbox or copied out via vm_get_file.

Instructions

Analyze one PE binary (headers, sections, imports, exports, version resource).

Works on a file extracted INSIDE the VM sandbox or copied out with vm_get_file. Reports interface facts only — no disassembly, nothing shippable from the binary.

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": "analyze_pe"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Oct 3, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose an important scope boundary ('no disassembly, nothing shippable from the binary'), which is genuinely useful behavioral context. But it says nothing about permissions, whether the target must be a running VM, or any side effects.

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?

Two short, front-loaded sentences: purpose first, then source and scope limitation. No filler, though the second paragraph packs source and limitations together without much structure.

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 purpose, input source, and scope limits. For a single-parameter analysis tool this is nearly complete; the missing piece is any note on environment prerequisites or read-only safety.

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 description coverage is 0% for the single 'path' parameter, so the description must compensate. It does clarify the origin of the file (inside the VM or copied out via vm_get_file), which gives the agent some semantic grounding for what path means, but it omits format, relative vs absolute, and sandbox path conventions.

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 (Analyze) and resource (PE binary), then enumerates exactly what is extracted: headers, sections, imports, exports, version resource. This is precise enough to distinguish it from siblings like dump_api_surface or iso_inspect.

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?

The description tells the agent where the input file must come from ('extracted INSIDE the VM sandbox or copied out with vm_get_file'), which is real usage context. However, it never states when to choose this over related siblings (dump_api_surface, iso_inspect) or any preconditions beyond file origin.

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