Skip to main content
Glama

uninstall_project

Destructive

Deletes a project's sandbox container, volume, and generated tools to clean up installed MCP projects.

Instructions

Remove a project: deletes its sandbox container, its volume and its generated tools.

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": {
      "project": "<project>"
    },
    "name": "uninstall_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesInstalled project: its slug, or its id such as "github:owner/name".

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?

The destructiveHint annotation already flags this as a write/destroy operation, so the description's added value is in specifying the blast radius: container, volume and generated tools all disappear. That is genuine context beyond the annotation. It falls short of a 5 because it does not state irreversibility, whether data in the volume is recoverable, or whether confirmation is expected.

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?

One sentence, front-loaded with the action and followed by the concrete consequences. Every clause earns its place and nothing is padded.

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 one-parameter mutation with full schema coverage and no output schema, the description covers what an agent most needs to know before calling: what gets deleted. Remaining gaps (recoverability, post-conditions of the response) are minor for a tool of this complexity.

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 already documents accepted forms (slug or id such as "github:owner/name"). The description adds no additional meaning about the project identifier, which is acceptable at baseline given the schema does the work.

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 ("Remove") and resource ("a project") and immediately enumerates the concrete artifacts destroyed: sandbox container, volume, generated tools. This makes it clearly the inverse of install_project among the siblings. It stops short of naming the counterpart tool explicitly, so sibling differentiation is inferred rather than stated.

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: the agent can infer this is the teardown call for an installed project. There is no explicit when-to-use vs when-not framing, no note that the project must currently be installed, and no mention of an alternative (such as simply deselecting tools) for less destructive cleanup.

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