Skip to main content
Glama
ngeojiajun

Code Snippet Server

by ngeojiajun

delete_snippet

Remove a specific code snippet by its ID to manage storage efficiently on the Code Snippet Server.

Instructions

Delete a snippet (specify ID)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of snippet to delete

Implementation Reference

  • Main tool handler: validates the snippet ID, delegates deletion to the storage engine, and returns success or not-found response.
    private async deleteSnippet(args: any): Promise<GenericMCPResponse> {
      if (!args || typeof args.id !== 'string') {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid snippet ID');
      }
    
      if (await this.engine.DeleteSnippet(args.id)) {
        return {
          content: [{
            type: 'text',
            text: this.getLocalizedString("snippet_deleted", args.id)
          }]
        };
      }
      return {
        content: [{
          type: 'text',
          text: this.getLocalizedString("snippet_not_found", args.id)
        }]
      };
    }
  • src/index.ts:87-99 (registration)
    Tool registration in the list tools handler, including name, localized description, and input schema requiring 'id'.
      name: 'delete_snippet',
      description: this.getLocalizedString("tool_delete_snippet"),
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: this.getLocalizedString("snippet_schema_id_to_delete")
          }
        },
        required: ['id']
      }
    }
  • Input schema for the delete_snippet tool, specifying a required 'id' string.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: this.getLocalizedString("snippet_schema_id_to_delete")
        }
      },
      required: ['id']
    }
  • Storage engine implementation: filters out the snippet by ID from local file storage and persists the change.
    async DeleteSnippet(id: string): Promise<boolean> {
      const initialLength = this.snippets.length;
      this.snippets = this.snippets.filter(s => s.id !== id);
    
      if (this.snippets.length < initialLength) {
        await this.saveSnippets();
        return true;
      }
      return false;
    }
  • Interface definition for the DeleteSnippet method in the storage base.
    DeleteSnippet(id: string):Promise<boolean>
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose that this is a destructive operation (implied by 'Delete'), whether it's reversible, what permissions are needed, or what happens on success/failure.

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?

The description is extremely concise with a single, clear sentence that front-loads the essential information. There is zero wasted text, making it efficient for quick understanding.

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

Completeness2/5

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

Given this is a destructive tool with no annotations and no output schema, the description is incomplete. It lacks crucial context like behavioral effects, error handling, or return values, leaving significant gaps for safe and effective use.

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?

Schema description coverage is 100%, so the schema already documents the 'id' parameter fully. The description adds no additional meaning beyond what's in the schema, such as format examples or constraints, meeting the baseline for high coverage.

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

Purpose4/5

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

The description clearly states the action ('Delete') and target resource ('a snippet'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'create_snippet' or 'list_snippets' beyond the obvious verb difference, missing explicit comparison.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing snippet ID), exclusions, or comparisons to siblings like 'list_snippets' for finding IDs first.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ngeojiajun/mcp-code-snippets'

If you have feedback or need assistance with the MCP directory API, please join our Discord server