wundervault
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WUNDERVAULT_MOCK | No | ||
| WUNDERVAULT_AGENT_KEY | No | ||
| WUNDERVAULT_AGENT_NAME | No | ||
| WUNDERVAULT_AGENT_TOKEN | No | ||
| WUNDERVAULT_AGENT_VAULT_URL | No | ||
| WUNDERVAULT_CREDENTIALS_FILE | No | ||
| WUNDERVAULT_AGENT_VAULT_API_KEY | No |
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 |
|---|---|
| vault_statusA | Report why vault tools are unavailable in this session and whether the credential has since been released. Returns no secrets. |
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
Only one tool exists, so there is no possibility of overlap or misselection; an agent can trivially identify its purpose.
vault_status uses a clear snake_case noun_status pattern; with a single tool, consistency is trivially satisfied.
A single tool for a server named wundervault is an extreme mismatch: it only reports why vault tools are unavailable, meaning the actual vault functionality is absent.
There are no tools for creating, reading, updating, or deleting secrets, nor for vault authentication or credential lifecycle. The surface is severely incomplete for a vault service, leaving agents with no real operations.