Skip to main content
Glama

triage_binary

Perform static triage on ELF, PE, Mach-O, and DEX files to extract architecture, bitness, language, hardening flags, linked libraries, sections, and SHA-256.

Instructions

Fast static triage of ELF/PE/Mach-O/DEX: arch, bits, language, hardening flags, linked libs, sections, SHA-256.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that triage is static and fast, implying no execution, and lists returned fields, but it does not state read-only safety, permission requirements, file-size limits, or error behavior.

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 dense sentence with zero waste. The core action and supported formats are front-loaded, followed by the returned fields.

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?

For a simple one-parameter tool with no output schema, the description is nearly complete: it names supported formats and enumerates the returned fields. It could be stronger with explicit usage guidance, but nothing essential for calling the tool is missing.

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 coverage is 100% and the single path parameter is already documented in the schema. The description adds no further meaning about the path parameter, so the baseline of 3 is appropriate.

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 and resource: static triage of ELF/PE/Mach-O/DEX files. It enumerates the exact outputs (arch, bits, language, hardening flags, linked libs, sections, SHA-256), which clearly distinguishes it from siblings like disassemble_function or extract_strings.

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 "Fast static triage" implies initial reconnaissance, but there is no explicit when-to-use guidance, no exclusions, and no comparison to alternatives such as apk_inspect or imports_exports. Usage is only implied.

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