Skip to main content
Glama

binary-forensics

binary_triage

Inspect a binary for magic header signature, Shannon entropy (packing/encryption detection), UPX markers, and ASCII/UTF-16LE strings.

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

Input Schema

NameRequiredDescriptionDefault
minLenNo
hexDataNo
filePathNo
base64DataNo
maxStringsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only inspection and lists which checks run, which is genuine disclosure, but it says nothing about resource limits on large binaries, whether inputs are mutually exclusive, or what form the results take (heuristic verdicts? raw entropy value? marker offsets?). For a multi-analysis forensic tool with zero annotation coverage, these omissions are material.

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 well-formed sentence with the resource front-loaded and the analysis list in order of execution; nothing is padded or redundant. It is arguably over-compressed for the amount of undocumented behavior, but that is a completeness problem rather than a verbosity one.

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

Completeness2/5

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

With no annotations, no output schema, five undocumented parameters, and no return-value information, the definition is not sufficient for an agent to call the tool confidently. The only thing fully covered is the list of analyses; input selection, limits, and result shape are all missing, which is disproportionate to this tool's complexity.

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% across five parameters, and the description supplies no parameter guidance whatsoever. The three alternative input channels (filePath, hexData, base64Data) and their precedence/ mutual exclusivity are completely undocumented, which is the single most likely source of a failed invocation. Only a weak inference exists that minLen and maxStrings relate to the 'ASCII/UTF-16LE strings' step.

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 names a specific verb+resource ('Inspect a binary') and enumerates the concrete analyses performed: magic header signature, Shannon entropy for packing/encryption detection, UPX markers, and ASCII/UTF-16LE strings. That is enough for an agent to distinguish it from a hex dumper (hexdump_inspect) or a disassembler, but it never explicitly contrasts itself with close siblings like executable_inspect or wasm_inspect, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all — no statement of which situations call for triage versus a deeper inspection tool, no prerequisites (e.g., size limits, whether the binary must be unpacked first), and no exclusions. The implied context is 'you have a suspicious binary,' but the agent must infer that entirely. Sibling tools such as executable_inspect and hexdump_inspect are not referenced even implicitly.

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