Skip to main content
Glama

wasm-mcp

by io.github.xyzzylabs

instruction_list

Read-only

Enumerate WebAssembly instructions, filterable by category, introduced_in (1.0|2.0|3.0), mnemonic prefix, and can_trap (only trapping / only non-trapping). Rows (incl. can_trap) sorted by opcode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoMnemonic prefix, e.g. `i32.`. Case-insensitive.
can_trapNoKeep only instructions that can (true) / cannot (false) trap.
categoryNoInstruction category.
introduced_inNoIntroducing version.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotation readOnlyHint already signals safety; description adds sort order and inclusion of can_trap, but no details on pagination, rate limits, or output structure.

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

Conciseness5/5

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

Single sentence with verb front-loaded, minimal but informative, no wasted words.

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?

Missing output schema, but description mentions key output fields (can_trap, opcode sort). For a filterable list with 4 optional params, it's largely complete.

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

Parameters3/5

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

Schema coverage is 100%, so description adds modest value (e.g., prefix case-insensitivity, enum listing), but no deep semantics beyond schema.

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?

Description states a specific verb 'Enumerate' and resource 'WebAssembly instructions', lists all filterable parameters, and distinguishes from siblings like instruction_search and instruction_get by focusing on listing with filters.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance relative to siblings, but the filtering capabilities imply its role as a listing tool against a single instruction or search tool.

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

All wasm-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct aspect of WebAssembly: instructions (get/list/search), proposals (list), spec sections (get/list/search), version info, and types. No overlapping purposes.

Naming Consistency5/5

All tools use consistent snake_case with verb_noun pattern: instruction_get, instruction_list, instruction_search, proposal_list, section_get, section_list, spec_search, spec_version, type_get.

Tool Count5/5

9 tools is well-scoped for a WebAssembly reference server, covering instructions, specs, proposals, types, and metadata without being overwhelming.

Completeness4/5

Covers core retrieval and search for instructions, specs, proposals, and types. Minor gaps like no dedicated proposal get or type list, but the set is sufficient for typical exploration tasks.

Resources