Skip to main content
Glama
Sign In

A2UI Atomic Catalog

by ai.a2uicatalog
OverviewDiscussionsAdmin

wasm_spike

Read-only

Diagnostic (MCP Apps hosts only): mounts a view that instantiates a tiny hand-assembled WebAssembly module, computes per-frame state in it, renders to canvas, and captures arrow-key input -- the same three ingredients a WASM game port would need. Answers whether THIS host permits WASM execution inside a ui:// View iframe; it proves nothing about any other host or sandbox.

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_spike"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description still adds real context: the tool physically mounts an iframe view, drives a WASM instance, and captures keyboard input, which is the kind of side effect an agent wouldn't infer from annotations. It does not say what a failed probe looks like or how the verdict is surfaced, which keeps it below a 5.

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 controlling constraint is front-loaded in parentheses, then the mechanism is listed as three concrete ingredients, then the scope limitation. The sentence is long and dash-heavy but every clause (three ingredients, ui:// iframe, host-specificity) carries information.

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?

With no parameters, no output schema and a narrow diagnostic scope, the description covers what an agent needs: what it does, the mechanism it exercises, and the bounds of what a result means. The one omission is how the outcome is reported to the caller (visual verdict vs. tool response), which matters given there is no output schema.

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?

The tool takes zero parameters, so the schema carries nothing the description needs to compensate for. Nothing about arguments is left ambiguous.

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?

The description names a specific verb-and-resource ('mounts a view that instantiates a tiny hand-assembled WebAssembly module ... renders to canvas ... captures arrow-key input') and states the exact question it answers. It is clearly distinguishable from the rendering/publishing siblings, which do not probe host capabilities.

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?

Gating is explicit: '(MCP Apps hosts only)' tells an agent when not to call it, and 'it proves nothing about any other host or sandbox' prevents over-generalizing the result. No sibling alternative is named, so it stops short of full when/when-not/alternative guidance.

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

All A2UI Atomic Catalog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources