33GOD Pipeline MCP 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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_domainsA | List the tool domains available in this hub. START HERE. Each domain bundles many underlying tools that are intentionally NOT loaded into your context yet. Returns each domain's name, title, description, tool_count, and load status. To use a domain, call list_domain_tools(domain) to load its tool schemas, then invoke a tool with call_domain_tool(domain, tool, arguments). |
| list_domain_tools | Load and list the tools in a domain, each with its name, description, and input_schema. Call this only for a domain you actually intend to use — it is what brings that domain's tool schemas into context. Then call call_domain_tool(domain, tool, arguments) to invoke a specific tool. |
| call_domain_toolA | Invoke a specific tool within a domain and return its result.
|
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: list_domains for discovery and call_domain_tool for invocation. No overlap at all.
Both tools follow a consistent verb_noun snake_case pattern (list_domains, call_domain_tool), making them predictable and clear.
With only 2 tools, the set feels thin, but for a hub server that delegates to domains, this minimal surface is acceptable and focused.
The hub is missing the list_domain_tools tool, which is advertised in list_domains' description. Without it, users cannot discover and invoke tools within domains, causing a critical gap.