Skip to main content
Glama

binary-forensics

wasm_inspect

Inspect a WebAssembly (.wasm) binary module for sections, function signatures, imports, exports, and linear memory page allocations.

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

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 burden. It does disclose the shape of the result (sections, signatures, imports/exports, memory pages) and implies a non-mutating inspection, but it says nothing about how the binary is supplied, whether it validates or fails on malformed modules, or whether it handles text-format .wat input.

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 a clear verb and an explicit enumeration of reported artifacts; no filler. It could be marginally better by spending the same words on input handling rather than only on output scope.

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?

No annotations and no output schema, so the description is the only behavioral source, and it leaves the two input parameters entirely unexplained plus nothing on error behavior or required inputs (0 required parameters means the caller must know at least one must be supplied). Adequate on what it extracts, inadequate on how to invoke 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% and both parameters (filePath, base64Data) are undocumented in both schema and description. The phrase 'a WebAssembly (.wasm) binary module' only loosely hints that a binary or path is supplied, and the description never explains the relationship between the two input options or whether either is required.

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?

Specific verb (Inspect) plus specific resource (WebAssembly .wasm binary module), and it enumerates exactly what gets reported: sections, function signatures, imports, exports, linear memory page allocations. That enumeration separates it in spirit from a disassembler sibling, though it never names an alternative explicitly.

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 or when-not-to-use guidance, no mention of prerequisites, and no pointer to a sibling such as disassemble_wasm_or_hex for the case where instruction-level output is needed. The reader must infer from the enumerated outputs that this is a structural/metadata inspection rather than a code disassembly.

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