Skip to main content
Glama

Code: show source control

code_show_source_control
Read-only

Opens the Source Control view in VS Code's activity bar and waits for its content to load, letting agents drive version control actions through the accessibility API.

Instructions

Select the Source Control 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_source_control"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: it blocks until content appears, and it will report a failure when the view was already selected and the sidebar collapsed — an agent needs to know a benign failure result is possible. It stops short of describing timeouts or what happens if VS Code isn't running.

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, front-loaded with the action, with the second sentence devoted entirely to the failure-mode caveat. No filler and nothing repeated from the schema 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?

For a zero-parameter, read-only UI-navigation tool with no output schema, the description covers the action, the wait semantics, and the misleading-failure case. Minor gaps remain around timeout behavior and the not-running-editor case, but nothing an agent needs to invoke it correctly is missing.

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. The description correctly omits any parameter talk rather than padding.

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 a precise resource ('the Source Control view in the VS Code activity bar'), which cleanly separates it from the sibling view tools (code_show_explorer, code_show_search) without needing to name them.

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 resource name rather than stated: there is no 'use when' clause and no explicit pointer to the alternative view tools. The one condition it does supply is a caveat (already-selected view collapses the sidebar), which is guidance about a pitfall rather than about when to choose this tool.

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