Skip to main content
Glama

Inspect Wasm Artifact

inspect_wasm_artifact
Idempotent

Validates a local WASM artifact with WABT, returning byte SHA-256, sections, import/export WAT forms, and decoded WAT evidence; use summary detail for counts and validation without WAT text.

Instructions

Validate an explicit local WASM artifact with caller-supplied WABT 1.0.42. Omitted or complete detail returns exact byte SHA-256, sections, upstream import/export WAT forms and decoded WAT inline as Evidence. For counts, validation and WAT identity without WAT text, pass detail: "summary" on this first call; it retains the complete original Evidence and returns the same typed summary as inspect_analysis_view, avoiding oversized complete delivery. Read exact imports/exports or WAT pages with inspect_analysis_view using normalized_result.parent_evidence_id. Delivery selection does not change analysis, provider inputs or source identity. Optionally associate selected JavaScript glue literals with explicit local candidates while preserving ambiguous URL/basename matches. Configure absolute REA_WABT_BIN_DIRECTORY. No installation, implicit fetch, WASM execution or original-source claim.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/artifacts/module.wasm",
      "glue_paths": [],
      "candidate_paths": []
    },
    "name": "inspect_wasm_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute selected local WASM artifact path
detailNo
glue_pathsNo
candidate_pathsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the evidence-retention model (summary still keeps the complete original Evidence), that delivery choice does not alter analysis/provider inputs/source identity, and explicit non-behaviors (no installation, implicit fetch, WASM execution, or original-source claim). The gap is that readOnlyHint=false and openWorldHint=true are left unexplained — it never says what it writes or why it is not read-only, which matters for an inspection tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and free of filler, but the sentences are long, jargon-dense, and several clauses ('Delivery selection does not change analysis, provider inputs or source identity') sit in the middle of an already packed paragraph. It is informative yet harder to parse than a bulleted purpose/delivery/handoff structure would be.

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 4-parameter tool with no output schema, the description supplies what is returned (SHA-256, sections, import/export WAT forms, decoded WAT as Evidence), how to get a lighter summary, and how to page the full result elsewhere. What is thin is the side-effect/annotation reconciliation (readOnlyHint=false, openWorldHint=true) and any failure behavior when WABT is misconfigured.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 25% schema description coverage, the prose must carry the load, and it largely does: detail is explained with its "summary" vs omitted/complete semantics and downstream effect, and glue_paths/candidate_paths are described as associating selected JavaScript glue literals with explicit local candidates while preserving ambiguous URL/basename matches. The mapping from prose to parameter names is implicit rather than named, which costs a point.

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 (validate/inspect), a specific resource (an explicit local WASM artifact) and the toolchain used (caller-supplied WABT 1.0.42). It is clearly separable from inspect_analysis_view, which is named as the paged-read surface, and from managed/external artifact inspectors by the 'explicit local' qualifier.

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

Usage Guidelines4/5

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

Gives concrete when-to-use routing: pass detail: "summary" when only counts/validation/identity are needed, and use inspect_analysis_view with normalized_result.parent_evidence_id when exact imports/exports or WAT pages are required. It also states the REA_WABT_BIN_DIRECTORY prerequisite. It does not contrast against the other local-artifact siblings (inspect_artifact, inspect_managed_artifact), so 4 rather than 5.

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

Deploy Server

Other Tools