Skip to main content
Glama
Sign In
vscode-mcp-server

vscode-mcp-server

by chaworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

install_extension

Install a VSCode extension by providing its ID, giving you access to additional features and tools within the editor.

Instructions

Installs 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": "install_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
extension_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not disclose idempotency, network requirements, version resolution behavior, or potential side effects, which are important for an installation operation.

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, front-loaded sentence with no redundancy. Every word contributes to conveying the basic purpose.

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

Completeness2/5

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

Despite having an output schema, the description leaves out essential context for a tool with no annotations: success/failure behavior, whether installation is idempotent, potential network dependencies, and how to obtain the extension ID. The description is too thin for a complete tool contract.

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?

The schema has no description for extension_id, and the description's phrase 'by its ID' adds only minimal value beyond what the parameter name already implies. It fails to clarify the expected format, such as publisher.extension naming convention.

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 a specific verb ('installs') plus the resource ('VSCode extension') and the key scope ('by its ID'). It naturally distinguishes itself from sibling tools like uninstall_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 Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as uninstall_extension or list_extensions. There is also no mention of prerequisites like needing the exact extension ID or checking existing installations.

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