Skip to main content
Glama

Inspect Macho

inspect_macho
Idempotent

Inspect Mach-O slices, load commands, imports, exports, dependencies, build metadata, segments, sections, permissions, and exact command provenance without launching Hopper.

Instructions

Inspect Mach-O slices, load commands, imports, exports, dependencies, build metadata, segments, sections, permissions, and exact command provenance without launching Hopper.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The description usefully discloses that the tool does not require launching Hopper, which tells the agent the operation is cheap and GUI-independent — and this is consistent with idempotentHint=true and destructiveHint=false. However, annotations declare readOnlyHint=false and openWorldHint=true, which is unusual for an inspector, and the description says nothing about side effects (caching, temp files, external lookups) that would explain those flags. It also never states what the target binary is or how it is supplied.

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 front-loaded sentence with the resource named first and the Hopper contrast last; nothing is redundant. The enumeration of artifact types is long but each item adds discriminative information about the tool's coverage.

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?

With no input schema properties and no output schema, the description is the only source of information about the call contract, and it omits how the Mach-O target is identified and what the response shape looks like. The list of inspected facets partially compensates, giving a good sense of the returned content. For a zero-parameter tool this leaves a meaningful gap around invocation.

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?

The tool takes zero parameters, so per the baseline the schema carries the full parameter burden and the description need not document arguments. The description does not invent or misdescribe any inputs. It could reach 5 only by explaining how the inspected file is selected when no parameters exist, which is the one genuine semantic gap.

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 opens with a specific verb and resource ("Inspect Mach-O slices") and enumerates exactly what is reported: load commands, imports, exports, dependencies, build metadata, segments, sections, permissions, and provenance. That is far more concrete than a generic "analyze binary" statement. It stops short of 5 because it never contrasts itself with close siblings such as inspect_binary_layout or inspect_native_load_image, so the agent must infer the boundary.

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 phrase "without launching Hopper" implies the usage context: fast static metadata extraction as a lightweight substitute for a full disassembler. There is no explicit when-to-use/when-not-to-use statement and no named alternative tool, so the routing guidance is implied rather than stated.

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