snippet-vault
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_snippetB | Save a code snippet to your personal vault |
| search_snippetsA | Search your saved snippets by title, language, tag, or content |
| get_snippetB | Get a specific snippet by its ID |
| list_snippetsA | List all saved snippets (titles and IDs only) |
| delete_snippetB | Delete a snippet from your vault by ID |
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 5 tools
Each tool targets a distinct operation (create, read, list, search, delete) with no overlap in purpose. An agent can clearly differentiate them.
All tools follow a verb_noun pattern. Minor inconsistency: 'list_snippets' uses plural noun while others use singular, but the pattern is clear and predictable.
With 5 tools, the server covers all essential operations for a snippet vault without being excessive or sparse. Each tool contributes meaningfully.
The tool surface includes create, read (by ID, list, search), and delete operations. An update operation is missing, but snippets are often immutable, so this is acceptable.