@tootega/dase-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DASE_MCP_URL | No | Override to skip discovery, directly use this URL | |
| DASE_MCP_DISCOVERY_DIR | No | Extra discovery directory for the proxy |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dase_statusA | Report the connection status between this MCP proxy and the DASE ORM Designer running in VS Code, with instructions to bring the designer online. |
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 ambiguity between tools.
A single tool cannot be inconsistent; the name 'dase_status' follows a clear noun-based pattern.
One tool is minimal and feels thin for a server, even if it covers a single purpose; borderline for typical scoping.
The tool completely covers its stated purpose of reporting connection status and providing instructions, with no obvious missing functionality.