Skip to main content
Glama
Sign In
Snippet Saver

Snippet Saver

by Grayhood144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

save_snippet

Stores a code snippet to a local snippets library as a file, named by the user, with language and optional description.

Instructions

Save a code snippet to your snippets library. The snippet will be saved as a file in ~/snippets/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "language": "<language>",
      "code": "<code>"
    },
    "name": "save_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code snippet to save
nameYesName for the snippet (will be used as filename)
languageYesProgramming language (e.g., javascript, python, java)
descriptionNoOptional description of what this snippet does

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It reveals the file location (~/snippets/), which adds value, but does not disclose behavior on conflicts (e.g., overwrite), permissions, or side effects. Basic but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both essential: the action and the storage location. No redundant information. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of a save operation and a fully-described schema, the description covers the key context (where it saves). It lacks details on overwrite behavior or error handling, but these are minor for this tool. Still above average.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, parameters are already well-documented. Description adds no extra meaning beyond what the schema states, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Save a code snippet to your snippets library.' It specifies the resource (code snippet) and destination (~/snippets/), distinguishing it from sibling tools list_snippets and read_snippet which retrieve or view snippets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage for saving snippets, it provides no explicit guidance on when to use this tool versus alternatives. Siblings are different operations, so context is implied, but no when-not-to-use or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools