Skip to main content
Glama
Sign In
gpu-mcp

gpu-mcp

by MYaelMendez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rust_build_wasm

Compile Rust crates to WebAssembly for use in web and edge applications.

Instructions

Compile a Rust crate to wasm32-unknown-unknown (local).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "crate_dir": "<crate_dir>"
    },
    "name": "rust_build_wasm"
  }
}

Input Schema

NameRequiredDescriptionDefault
crate_dirYespath to cargo crate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'compile' and 'local', but does not disclose side effects, prerequisites (e.g., target installed), or output details.

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?

Single concise sentence with no filler. Appropriate length given simplicity.

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?

Tool is simple but lacks output description. No mention of what is produced (e.g., .wasm file), which is needed since no output schema exists.

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 description coverage is 100% for the single parameter 'crate_dir'. Description adds no additional meaning beyond the 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?

Clearly states verb 'Compile', resource 'Rust crate', target 'wasm32-unknown-unknown', and location 'local'. Distinguishes from siblings like rust_run_wasm and compile_kernel.

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?

Implied usage (build before run), but no explicit when-to-use or when-not-to-use compared to alternatives. No exclusion statements.

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