Skip to main content
Glama

binary-forensics

executable_inspect

Parse Linux ELF32/64, Windows PE32/PE32+, and macOS Mach-O / Universal binary headers, sections, entry points, and exploit mitigations (PIE, ASLR, NX, RELRO, CFG).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It helpfully discloses what the tool surfaces (headers, sections, entry points, and specific mitigations such as PIE, ASLR, NX, RELRO, CFG), but never states that the operation is a side-effect-free read, nor how it behaves on malformed/truncated binaries or oversized inputs.

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?

A single sentence, front-loaded with the verb and the platforms covered, then the extracted artifacts. Every clause earns its place with no filler or repetition.

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

Completeness3/5

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

There is no output schema and no annotations, so the description must do the work alone. It compensates well for the missing output schema by naming what is extracted, but leaves the two input parameters and error/edge behavior entirely undocumented for a two-parameter tool.

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% and the description mentions neither filePath nor base64Data. It gives no indication that a file can be supplied by path or inline as encoded bytes, nor whether the two are mutually exclusive, so the agent must inspect the raw schema to understand either parameter.

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?

The description uses a specific verb ("Parse") and enumerates the exact resource classes handled: Linux ELF32/64, Windows PE32/PE32+, and macOS Mach-O/Universal, plus the fields extracted (headers, sections, entry points, mitigations). That format list effectively separates it from siblings like wasm_inspect and hexdump_inspect, though it never names an alternative explicitly.

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?

Usage is only implied by the format enumeration: an agent can infer it should call this for native ELF/PE/Mach-O binaries rather than WASM or raw hex dumps. There is no explicit when-to-use statement, no exclusion, and no guidance on which of the two input modes to choose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources