Skip to main content
Glama

Code: show explorer

code_show_explorer
Read-only

Opens the Explorer view in the VS Code activity bar and waits for its content to appear, reporting failure if the view is already selected and collapses the sidebar instead.

Instructions

Select the Explorer view in the VS Code activity bar and wait for its content to appear. Pressing the already-selected view collapses the side bar instead; that reports honestly as a failure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "code_show_explorer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint true, destructiveHint false, closed-world), so the bar is lower. The description still adds genuine value by disclosing a non-obvious failure mode: re-invoking on an already-selected view collapses the sidebar. It does not state a timeout or what 'content to appear' means operationally.

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?

Two sentences, both load-bearing: the first defines the action and its wait condition, the second covers the sole edge case. Nothing is repeated from the title or annotations.

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?

With no parameters and no output schema, the description needs only to explain the action and its failure semantics, which it does. The remaining gap is minor: no indication of how long it waits or what an agent should do on the reported failure (e.g., retry vs. assume the view is already visible).

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No misleading parameter language is present.

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?

States a specific verb (select) and resource (the Explorer view in the VS Code activity bar) and adds the completion condition (wait for content to appear). Among siblings like code_show_search and code_show_source_control, naming the exact target view makes selection unambiguous.

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?

The description makes the triggering context explicit (open the Explorer view) and warns about the one case where calling it backfires — when the view is already selected, the sidebar collapses and the call reports a failure. It does not explicitly route to sibling view tools, but the named target view does that implicitly.

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