Code Snippet Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_snippetC | Create a snippet (specify title, language, and code) |
| list_snippetsC | List snippets (can filter by language or tags) |
| delete_snippetC | Delete a snippet (specify 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 3 tools
Each tool has a clearly distinct purpose: create_snippet for creation, delete_snippet for deletion, and list_snippets for listing with optional filtering. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern (create_snippet, delete_snippet, list_snippets) using snake_case throughout. This makes the set predictable and easy to understand.
With only 3 tools, the set feels thin for a snippet management server. While it covers basic operations, it lacks tools for updating snippets or retrieving a single snippet by ID, which are common needs in such domains.
The server provides create, delete, and list operations, but there are notable gaps: no update_snippet tool to modify existing snippets and no get_snippet tool to retrieve a specific snippet by ID. This limits functionality and may cause agent workarounds.