Skip to main content
Glama

skillporter_remove

Destructive

Removes an installed AI agent skill from target harnesses in a workspace; write operations require SKILLPORTER_MCP_ALLOW_WRITES=1.

Instructions

[WRITE] Remove an installed skill from target harnesses in the workspace (requires SKILLPORTER_MCP_ALLOW_WRITES=1).

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": {
      "skill": "<skill>"
    },
    "name": "skillporter_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
skillYesSingle-segment skill name to remove
harnessesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not the sole source of safety information; the [WRITE] tag simply echoes that. It adds real value by disclosing the SKILLPORTER_MCP_ALLOW_WRITES=1 requirement, but says nothing about what is actually destroyed (files vs. registration entries), reversibility, or behavior when the skill is absent from a listed harness.

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?

A single front-loaded sentence with the [WRITE] marker leading, the action and scope next, and the precondition parenthesized. Nothing is wasted and the most decision-relevant facts come first.

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

Completeness3/5

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

For a destructive, three-parameter tool with no output schema, the definition covers the action and the write gate but leaves out failure modes, whether removal is reversible, and the semantics of the two undocumented parameters. It is adequate to attempt a call but not to predict its consequences.

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 only 33%: only 'skill' is described, leaving 'path' and 'harnesses' undocumented in the schema. The description partially compensates by framing harnesses as removal targets and the workspace as the scope, but it never clarifies single-vs-multiple harness selection, whether an omitted harnesses array means all harnesses, or what path is relative to.

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?

States a specific verb and resource: 'Remove an installed skill from target harnesses in the workspace'. The scope (harnesses, workspace) is explicit, so an agent can distinguish it from its install/add counterparts by name. It stops short of naming a sibling or explaining how removal relates to preview/sync, which keeps it from a 5.

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?

Usage is only implied by 'installed skill' and 'target harnesses'; there is no explicit statement of when to choose this over skillporter_add or skillporter_sync, nor what to do first. The write-gate prerequisite is stated, which is a genuine when-can-you-use condition, but there is no when-not guidance or warning to verify state first.

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