Skip to main content
Glama
Sign In
@quikrun/mcp

@quikrun/mcp

by exit150
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

delete_snippet

Permanently delete a snippet from QuikRun by its unique slug. Irreversible action, so confirm before use.

Instructions

[DESTRUCTIVE] Permanently delete a snippet by slug. This cannot be undone.

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": {
      "slug": "<slug>"
    },
    "name": "delete_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe snippet slug to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description takes on the full burden of behavioral disclosure. It includes '[DESTRUCTIVE]' and 'This cannot be undone,' which clearly warns about the irreversible nature of the deletion, a critical behavioral trait.

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 a single concise sentence with an emphasis tag. Every word adds value, and there is no filler or redundancy.

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?

For a simple one-parameter destructive tool with no output schema, the description covers the essential warning about permanence. However, it doesn't mention potential error conditions (e.g., slug not found) or permission requirements, which would be useful but are not strictly necessary.

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?

The input schema already fully describes the 'slug' parameter as 'The snippet slug to delete.' The description only echoes 'by slug' without adding format details, examples, or constraints, so it provides minimal extra value beyond the schema.

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 (delete), the resource (snippet), and the method (by slug). This distinguishes it from sibling tools like update_snippet or duplicate_snippet, which perform different operations.

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, such as update_snippet for modifying a snippet. It simply states the operation without contextual 'when to use' or 'when not to use' information.

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