wasmagent-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | API key for OpenAI or compatible endpoints (required if using OpenAI models) | |
| ANTHROPIC_API_KEY | No | API key for Anthropic model access (required if using Anthropic models) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"cancel": {},
"create": {},
"respond": {}
} |
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_searchA | Look up the available downstream tools by name or substring. Call this BEFORE writing an execute_code script to learn what's available. |
| execute_codeA | Run a JavaScript snippet inside a sandboxed kernel. The snippet may call |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: docs_search for discovering downstream tools, and execute_code for running code that calls them. There is no overlap or confusion.
Both tool names follow a consistent verb_noun pattern with snake_case: docs_search and execute_code.
Two tools is exactly right for this server's purpose as a meta-agent: search to discover, execute to run. It's minimal but complete.
The tool surface fully covers the intended workflow: discovering available downstream tools and executing code that chains them. There are no obvious gaps.