Skip to main content
Glama
autoworks-ai

AutoVault

by autoworks-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_skill

Remove an installed skill from the vault, refresh generated profiles, and prune managed consumer links. Set discover_profile_roots to false to skip discovery.

Instructions

Delete an installed skill from the vault and refresh generated profiles. Existing host skill roots are discovered by default so managed consumer links are pruned; pass discover_profile_roots: false to opt out. This also removes vault-local transforms for that skill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
profile_rootsNo
discover_profile_rootsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / discover_profile_roots
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / profile_roots
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It explains default host root discovery, the pruning of managed consumer links, the opt-out via discover_profile_roots: false, and the additional removal of vault-local transforms. This gives an agent a strong mental model of side effects beyond the basic delete action.

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 three sentences with no filler: the primary action and immediate effect come first, the configurable discovery behavior follows, and the additional transform removal closes it out. Every sentence earns its place and the structure is easy to parse.

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 destructive tool with no annotations and no output schema, the description covers the key behavioral surfaces well: what is deleted, what is refreshed, what is pruned, and how to opt out. The main missing piece is a clearer explanation of the profile_roots parameter's shape and purpose, which prevents this from being fully complete for advanced usage.

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 0%, so the description must compensate. It adds useful meaning for discover_profile_roots by explaining its default and the opt-out behavior, and 'name' is self-evident. However, the profile_roots object parameter is never explicitly explained or mapped to the 'host skill roots' concept, leaving a significant gap for an optional but non-trivial parameter.

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 opens with a specific verb and resource: 'Delete an installed skill from the vault', and immediately distinguishes this from all sibling tools whose names describe add/get/update/propose actions. The secondary effect of refreshing generated profiles is also stated, so an agent knows exactly what action is performed.

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

Usage Guidelines4/5

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

The purpose is unambiguous: deleting a skill is clearly the inverse of add_skill or update_skill, so the usage context is clear from the first sentence. It does not explicitly name alternatives or exclusion conditions, but the tool's destructive role among these siblings is obvious and the description gives actionable context for when to use it.

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