Skip to main content
Glama

artifact_remove

Destructive

Preview and delete X++ artifact XML, companion payloads, and indexed project memberships after impact analysis; actual removal requires confirm=true.

Instructions

Dry-run or remove artifact XML, any companion payload, and indexed project memberships after impact analysis; actual removal requires confirm=true.

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": {
      "path": "<path>"
    },
    "name": "artifact_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
limitNo
dryRunNo
confirmNo
projectPathNo
maximumDepthNo
solutionPathNo
expectedSha256No
projectExpectedSha256No
companionExpectedSha256No

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
actionNo
dryRunNo
impactNo
changesNo
artifactNo
previousIdNo
impactTruncatedNo
solutionValidatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known; the description adds real value by enumerating exactly what is destroyed (XML, companion payload, index entries) and disclosing the confirm=true gate plus dry-run default. It omits whether deletion is reversible and how the expectedSha256 guards behave on mismatch.

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?

One dense sentence with the scope front-loaded and the confirm requirement placed at the end where it matters most; no filler. The semicolon-joined clauses make it slightly packed, but every phrase carries information.

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?

With an output schema present, return values need no explanation, and the destructive path is reasonably well covered. However, for an 11-parameter destructive tool with zero schema descriptions, the undocumented hash guards and scoping parameters (root, projectPath, solutionPath, limit, maximumDepth) leave meaningful gaps before a safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, so the description carries the full explanatory burden, yet it only clarifies dryRun and confirm. The three expectedSha256 optimistic-concurrency guards, root, limit, maximumDepth, projectPath, and solutionPath get no meaning at all, leaving the agent to guess at their purpose.

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 names a specific verb (remove/dry-run) and an unusually precise resource scope: artifact XML, companion payload, and indexed project memberships. That scope separates it from artifact_update, artifact_build, and artifact_validate without the agent needing to open any schema.

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?

It establishes the operating sequence (dry-run first, real deletion only with confirm=true) and references impact analysis as a precondition, which tells the agent not to call it blindly. It stops short of naming the specific sibling to run for that analysis (e.g., reference_impact) or stating when removal should not be attempted.

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