Snippet Saver
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_snippetA | Save a code snippet to your snippets library. The snippet will be saved as a file in ~/snippets/ |
| list_snippetsA | List all saved code snippets in your library |
| read_snippetA | Read a specific code snippet from your library |
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 3 tools
Each tool has a clear and distinct purpose: listing all snippets, reading a specific snippet, and saving a new snippet. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (list_snippets, read_snippet, save_snippet) with underscore separation, making them predictable.
With 3 tools covering list, read, and create operations, the count is reasonable for a simple snippet library. It is slightly minimal but not inappropriate.
The set covers core operations (list, read, save) but lacks update and delete functionality, which are notable gaps for a snippet management tool.