Skip to main content
Glama

binary-forensics

hexdump_inspect

Generate an annotated hex + ASCII dump of a binary range with Shannon entropy classification and multi-endian int/float data inspection at offset.

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

Input Schema

NameRequiredDescriptionDefault
lengthNo
offsetNo
filePathNo
base64DataNo
bytesPerRowNo

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?

With no annotations, the description carries the full behavioral burden. It discloses the output content (annotated hex/ASCII, entropy classification, multi-endian interpretation) but says nothing about read-only safety, size limits, error behavior, or how conflicting input sources are resolved.

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 no filler; every clause maps to a capability. The dense noun-stack ('multi-endian int/float data inspection at offset') is slightly hard to parse but efficient.

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?

For a five-parameter tool with no annotations, no output schema, and 0% schema coverage, the definition is underspecified. It omits input-source rules, size constraints, and return-format details that an agent would need before calling it.

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, so the description must compensate and largely fails. It hints at 'offset' and a 'range' (length) plus the three display/analysis features, but never explains the critical filePath vs base64Data choice, bytesPerRow, or defaults.

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?

States a specific verb ('Generate'), resource ('annotated hex + ASCII dump'), scope ('binary range'), and two additional analyses (Shannon entropy classification, multi-endian int/float inspection at offset). An agent can tell this is a binary hex-dump analyzer, though it does not explicitly differentiate itself from siblings like executable_inspect or wasm_inspect.

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?

No when-to-use guidance is given: it does not say when to prefer this over executable_inspect/wasm_inspect, nor when to supply filePath versus base64Data. The agent must infer that this is for raw binary inspection without any routing signal.

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