Slash Command Manager
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| basic-exampleA | Return a static message for testing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| placeholder | A placeholder prompt for testing the slash command generator and MCP server |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no risk of confusion between tools. The single tool's purpose is clearly described.
With a single tool named 'basic-example', naming consistency is trivially maintained. The name uses a clear hyphenated pattern.
The server is titled 'Slash Command Manager' but provides only one test tool. This is far too few tools for the implied scope of managing slash commands.
The single tool is a static test example, offering no actual functionality for managing slash commands. The surface is severely incomplete relative to the server's purpose.