Skip to main content
Glama

binary-forensics

disassemble_wasm_or_hex

Disassemble WebAssembly (.wasm) bytecode into .wat text or decode x86-64, AArch64, and RISC-V machine code hex bytes.

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

Input Schema

NameRequiredDescriptionDefault
archNox86_64
hexDataNoHex machine code bytes (e.g. "55 48 89 e5 ...").
filePathNo
base64DataNo
baseAddressNo0x1000

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 burden of behavioral disclosure, yet it only says what conversion occurs. It does not state whether the operation is read-only, whether it reads files from disk, what permissions are needed, or how errors are reported.

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?

The definition is a single front-loaded sentence with no wasted wording, and it efficiently separates the WebAssembly and machine-code use cases. It is concise, though the two modes are not structurally distinguished beyond the word 'or'.

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 and no output schema, the description is too sparse. It omits input precedence, file access behavior, base address meaning, and return details, leaving an agent without enough context to call it reliably.

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 coverage is only 20%, so the description needs to compensate, but it mentions only hex bytes and the supported architectures. It says nothing about filePath, base64Data, baseAddress, or how the three input sources relate or take precedence.

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 uses specific verbs and resources: disassemble WebAssembly bytecode into .wat text, and decode x86-64, AArch64, and RISC-V machine code hex bytes. This clearly distinguishes the tool from generic inspection tools, though it does not explicitly name a sibling alternative.

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?

The description states what formats the tool handles but gives no guidance about when to choose it over siblings like wasm_inspect or hexdump_inspect. It also does not explain input-mode selection between filePath, hexData, and base64Data.

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