Skip to main content
Glama

remove_snippet

Delete a named saved text block from the Detour vault to clean up stored reusable content; requires edit permission.

Instructions

Remove a snippet (needs vault:edit).

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>"
    },
    "name": "remove_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesIts name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only discloses the auth requirement. It says nothing about irreversibility, what happens if the named snippet does not exist, or whether removal affects sessions or runs that already reference the snippet.

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

Conciseness4/5

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

It is a single short sentence with no wasted words and the verb is front-loaded. The terseness edges toward under-specification rather than verbosity, but structurally it is clean.

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?

For a destructive mutation with zero annotation coverage and no output schema, the definition should say what is destroyed and what the caller receives on success or failure. Only the permission requirement is covered, leaving significant gaps for a delete operation.

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 coverage is 100% and the single parameter "name" is documented, so the schema does most of the work. The description adds no naming conventions, case sensitivity, or path/identifier format, which is the baseline-3 outcome for a fully covered schema.

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 pairs a specific verb with a specific resource ("Remove a snippet"), which is enough to distinguish it from add_snippet, list_snippets, and run_snippet. It does not differentiate itself from the generic sibling "remove", leaving that boundary implicit.

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 only guidance is a prerequisite, "(needs vault:edit)", which is about permission rather than when to choose this tool. There is no statement of when-not to use it or which sibling (e.g. remove, run_snippet) to prefer, so usage is left to inference.

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