Skip to main content
Glama

Code: show search

code_show_search
Read-only

Selects the VS Code Search view and waits for its content to load, enabling GUI agents to open search reliably without screenshot-based automation.

Instructions

Select the Search 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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower, and the description still adds real context: the call blocks until the view content appears, and an already-selected view produces a sidebar collapse that surfaces as a failure. That failure semantics is non-obvious and prevents an agent from retrying blindly. It stops short of saying whether the failure is distinguishable from other errors or whether focus moves.

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 that each do work: the action plus its wait condition first, then the edge case. No restatement of the title and no filler, despite the slightly chatty "reports honestly" phrasing.

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 zero-param, no-output-schema UI navigation tool with read-only annotations, the description is close to sufficient: it covers the action, the blocking wait, and the failure mode. The remaining gap is sibling disambiguation from code_search_workspace, since an agent could reasonably mistake this for the tool that runs a search.

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 document and no gap to compensate for. Baseline 4 applies; the description correctly says nothing extraneous about inputs.

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?

Names a specific verb and resource ("Select the Search view in the VS Code activity bar") and names the host application, which separates it from the notes/textedit/slack siblings. It differentiates from code_show_explorer and code_show_source_control only implicitly, by resource name, and never disambiguates it from code_search_workspace, which actually performs a search.

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 implied by the verb: open the Search view. There is no statement of when to prefer this over code_search_workspace or when to prefer code_show_explorer. The one conditional it gives (pressing an already-selected view collapses the side bar) is a caveat, not a when-to-use rule.

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