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

vscode-mcp-server

by juehang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_extension_status

Verify that the VS Code MCP Extension is installed and responding within a specified project folder. Helps diagnose setup issues by confirming the extension's active status.

Instructions

Check if the VS Code MCP Extension is installed and responding

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": {
      "targetProjectPath": "<targetProjectPath>"
    },
    "name": "check_extension_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetProjectPathYesPath to the project folder we are working in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states the check action but does not confirm it is non-destructive, reveal side effects, or indicate required permissions. The agent cannot infer safety or scope.

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 concise sentence with no unnecessary words. It is front-loaded and efficient.

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 simple health check tool with one parameter, the description provides the core purpose. However, it lacks contextual details like read-only nature or usage flow, making it barely adequate.

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 description coverage is 100%, and the description adds no additional meaning beyond what the input schema already provides. Baseline 3 is appropriate as the schema does the work.

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 tool checks if the VS Code MCP Extension is installed and responding, providing a specific verb-resource pair. However, it does not differentiate from sibling tools like get_extension_port, but the purpose is unambiguous.

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 given on when to use this tool versus alternatives. There is no mention of prerequisites or context that would help an agent decide to invoke it, e.g., before other extension-related operations.

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