deprecated-legacy-sandbox
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVCLAMP_API_KEY | No | Your RevClamp workspace API key (starts with rg_live_...). Omit this to run in Stateless Sandbox Mode with zero database writes. |
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 |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| legacy_sandbox_noopB | No-op diagnostic stub for archived sandbox workspace. |
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
There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its no-op diagnostic role is clearly distinguishable by default.
The single tool name uses a clear snake_case pattern and is descriptive of its legacy sandbox no-op behavior. There is no mixed convention to penalize.
A single trivial no-op tool is an extremely thin tool surface for an MCP server, even one framed as deprecated. The rubric treats a single trivial tool as an extreme mismatch.
The surface offers no meaningful lifecycle operations such as listing, inspecting, updating, or cleaning up sandbox workspaces. For the stated archived sandbox domain, a no-op diagnostic stub is severely incomplete.