Skip to main content
Glama

Inspect Go Binary

inspect_go_binary
Idempotent

Extracts embedded Go build metadata—compiler version, modules, dependencies, and build settings—from local ELF, PE, or thin Mach-O binaries without executing or disassembling them.

Instructions

Inspect embedded Go compiler version, main module, dependency/replacement versions and build settings in an explicit local ELF, PE or thin Mach-O image. Returns original artifact SHA-256, exact build-info source ranges, raw framed module bytes and unparsed module-text lines inline as observed Evidence. Supports inline and historical pointer encodings without installing Go, opening a disassembler, executing the target, writing temporary files or accessing the network. Missing metadata is reported as unknown, not proof that an image is not Go. Does not recover functions, source mappings, types or runtime behavior. Resource guards bound files to 256 MiB, aggregate embedded strings to 1 MiB, structural table decoding to 16 MiB and complete inline metadata to 8 MiB; malformed, unsupported and oversized inputs receive typed failures rather than partial success.

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"
    },
    "name": "inspect_go_binary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute filesystem path to the selected executable or library

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral traits: no Go installation, disassembler, target execution, temporary files, or network access; missing metadata is reported as unknown rather than proof the image is not Go; and malformed/oversized inputs produce typed failures rather than partial success. It also states resource guard limits and the exact evidence returned.

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?

The description is long but front-loaded and dense with decision-relevant information. Each sentence adds purpose, constraints, return evidence, caveats, or failure behavior; there is no filler or repetition.

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

Completeness5/5

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

For a complex inspection tool with no output schema, the description is complete: it explains what evidence is returned, what is not recovered, how unknown metadata should be interpreted, and how malformed or oversized inputs are handled. An agent has enough context to call it correctly and interpret results.

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 100% for the single path parameter, so the baseline is 3. The description adds meaningful constraints beyond the schema by specifying that the path must point to an explicit local ELF, PE, or thin Mach-O image, which helps an agent avoid passing unsupported formats.

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?

The description uses a specific verb and resource: inspect embedded Go compiler version, main module, dependency/replacement versions, and build settings. It also names the exact accepted image types (ELF, PE, thin Mach-O), which clearly distinguishes it from generic binary-inspection siblings.

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 gives clear usage context for local Go build metadata and explicitly excludes non-goals such as recovering functions, source mappings, types, or runtime behavior. It does not name sibling alternatives such as inspect_binary_layout, so it stops short of full when-to-use routing.

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