wiswa-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_defaultsA | Get resolved default settings, optionally narrowed to a dot-separated key path. |
| lookup_settingA | Look up a setting by dot-separated key path and get its default value plus override snippet. |
| list_settingsA | List setting keys at a given path and depth. |
| search_settingsA | Search for settings by substring match on their fully-qualified key path. |
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 4 tools
Each tool has a clearly distinct purpose: getting resolved defaults, listing keys, looking up a specific setting, and searching by substring. No overlap in functionality.
All tools follow a consistent verb_noun pattern in snake_case (get_defaults, list_settings, lookup_setting, search_settings), making them predictable and easy to remember.
With 4 tools, the server is well-scoped for a settings management utility. Each tool covers a distinct operation without unnecessary bloat or deficiency.
The tool set covers the core operations for inspecting settings: retrieving defaults, exploring the key hierarchy, looking up specific keys, and searching. No obvious gaps for a read-only configuration server.