JavaScript Sandbox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_jsC | Execute JavaScript code in an isolated environment |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as executing JavaScript code in isolation, making it distinct by default.
The single tool name 'execute_js' follows a clear verb_noun pattern (execute + js). Since there is only one tool, consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server named 'JavaScript Sandbox MCP Server', which implies broader functionality like evaluating expressions, managing contexts, or handling errors. This minimal set feels thin and under-scoped for the apparent domain.
The tool surface is severely incomplete for a JavaScript sandbox domain. It lacks essential operations such as evaluating expressions, clearing contexts, handling errors, or managing state, which are typical for such environments, leading to significant gaps in functionality.