Skip to main content
Glama

Inspect Binary Layout

inspect_binary_layout
Idempotent

Inspect a local ELF binary without executing it to retrieve section/segment ranges, symbols, relocations, dependencies, and static mitigation evidence for layout analysis.

Instructions

Inspect an explicit local binary without launching it as a host process. Returns file-backed section/segment ranges, linked addresses, original symbol/REL/RELA table identities, complete encoded RELR tables and upstream-derived offsets with unknown per-word locations/addends, raw name bytes, dependency/interpreter names and static mitigation inferences inline with artifact SHA-256 Evidence. Initial profile: ELF64 x86-64 little-endian EXEC/DYN/REL on Linux x64 via caller-supplied Python with unchanged pwntools 4.15.0, pyelftools 0.33 and Unicorn 2.1.2. Runtime addresses/library paths, overall relocation inventory completeness and complete derived GOT/PLT coverage remain unknown. Zero executable entry values mean absence; relocatable entries are not applicable. Upstream can emulate PLT instructions with Unicorn for derived static maps. Uses bounded complete output and owned temporary files/processes; malformed, unsupported or oversized objects return no partial success. Select detail summary to retain the complete layout Evidence in this session and receive only its summary view, then inspect sections, symbols, mitigations or linkage with inspect_analysis_view.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/artifacts/application.elf"
    },
    "name": "inspect_binary_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute filesystem path to the selected binary
detailNofull/complete returns the complete analysis Evidence inline. summary retains that complete Evidence in this session and returns its inspect_analysis_view summary; inspect pages, items or facets through normalized_result.parent_evidence_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds real value beyond that by disclosing bounded output, owned temporary files/processes, all-or-nothing failure semantics, pinned upstream versions, and an explicit unknown list. However, it never explains the openWorldHint=true surface (no external/network behavior is described for a tool reading a local file), and the enumeration of returned evidence is dense enough that an agent cannot tell which fields are always present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but it is followed by a single sprawling sentence that fires off every returned artifact type at once. The most actionable instruction, the detail=summary plus inspect_analysis_view workflow, is buried at the very end and duplicates text already present in the schema.

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?

With no output schema, the description carries the full burden of describing returns, and it does list sections, addresses, REL/RELA/RELR tables, dependencies, mitigations, and SHA-256 Evidence, plus stated unknowns and failure behavior. It stops short of stating what the summary view actually contains or whether results are paginated beyond the parent_evidence_id hint.

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 100%, and the schema's detail property already spells out the full/complete vs summary retention semantics and the parent_evidence_id drill-down path. The description largely restates that contract at the end without adding new meaning for path or detail, so the baseline 3 applies.

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 first sentence pairs a specific verb and resource ("inspect an explicit local binary") with an important scope constraint ("without launching it as a host process"). The pinned "Initial profile: ELF64 x86-64 ... EXEC/DYN/REL" implicitly separates it from siblings like inspect_go_binary or inspect_macho, but the description never names those alternatives, so differentiation is left to inference.

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?

It explicitly routes the agent: choose detail=summary to retain full Evidence in-session, then drill into sections/symbols/mitigations/linkage via inspect_analysis_view. It also states the failure boundary (malformed/unsupported/oversized objects yield no partial success). What is missing is any explicit when-not guidance naming the sibling probes for Go, Mach-O, Rust/C++, or frozen Python artifacts.

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