vscode-mcp-server

by chaworld

Overview Schema Source Related Servers Discussions Admin

Python

Local

uninstall_extension

Uninstall a VSCode extension by providing its extension ID to remove it from the workspace.

Instructions

Uninstalls a VSCode extension by its ID.

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": {
      "extension_id": "<extension_id>"
    },
    "name": "uninstall_extension"
  }
}

Input Schema

Name	Required	Description	Default
`extension_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, permission requirements, whether the extension must already be installed, or the outcome of the operation beyond the action itself. For a destructive tool, this is a notable gap.

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 a single sentence that is front-loaded and contains no wasted words. It efficiently conveys the core action and parameter.

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?

The tool is simple with one parameter and a clear action, so the description covers the basic intent. However, since it is a destructive operation with no annotations or output schema information, additional context such as what happens on success, error cases, or installation prerequisites would make it more complete. The current description is minimally acceptable.

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?

The schema only provides the parameter name 'extension_id' with no description. The description adds that the extension is identified by its ID, which partially clarifies the parameter's semantics, but it does not define the expected format (e.g., 'publisher.name'). With 0% schema coverage, the description provides minimal but useful compensation.

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 clearly states the action: 'Uninstalls a VSCode extension by its ID.' The verb is specific, the resource is identified, and the input mechanism is noted, distinguishing it from sibling tools like install_extension and list_extensions.

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?

The description implies usage whenever an extension needs to be removed, but it does not explicitly state when to use it over alternatives or provide any context on prerequisites. No alternatives are mentioned, so the guidance is implied rather than explicit.

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

Deploy Server