DeepSeek Capability Hub
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| capability_hubA | Search and inspect a compact catalog, enable a trusted MCP only when needed, list its tools, proxy a tool call, or load one skill body. Action "tools" starts a stopped capability by itself, so "enable" is only for starting one deliberately. Avoid includeSchema unless you need the argument shape. Third-party proposals require human approval outside this MCP. Available capabilities — demo-echo (mcp): Bundled local MCP used to verify dynamic discovery, enable, tool listing, calls, and disable. | ml-experiment-review (skill): Review an ML experiment as a falsifiable, reproducible evidence package. |
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 between tools. The tool's sub-actions (search, enable, list, proxy, load skill) are clearly described within the single capability.
The single tool name 'capability_hub' is clear and uses snake_case. Since there is only one name, there are no inconsistencies or mixed conventions to evaluate.
A single tool for a capability hub is minimal but not trivial—it acts as a meta-interface to multiple sub-capabilities. The scope is narrow but the tool is comprehensive enough to justify its presence.
The hub covers the full lifecycle of capabilities: searching the catalog, enabling MCPs, listing tools, proxying calls, loading skills, and disabling (as referenced in the demo-echo example). No obvious gaps exist for the stated purpose.