Skip to main content
Glama

start

Allocate base and candidate VMs for a permitted local repository with uncommitted changes, using a Git commit reference as the base while leaving the host repository untouched.

Instructions

Allocate base and candidate VMs for a permitted local repository with uncommitted changes. Base is a Git commit reference such as HEAD. Leaves the host repository untouched.

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": {
      "repo": "<repo>",
      "base": "<base>"
    },
    "name": "start"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
repoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that it leaves the host repository untouched and that the repository must be 'permitted', hinting at a permission gate. It stops short of saying how long the allocated VMs persist or that a teardown step is required, but the safety-relevant behavior is well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler, and the core action is front-loaded in the first sentence. The base-parameter note sits mid-paragraph rather than being grouped, but nothing is wasted.

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 two-parameter start operation with no output schema, the description should say what the agent receives back (VM handles/IDs) and how the allocation is later released. Neither is covered, so an agent knows what the tool does but not what to do with the result.

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 0%, so the description must carry parameter meaning; it partially does by explaining base as a Git commit reference such as HEAD and implying repo is a local repository. The repo parameter's expected form (path, name, or identifier) remains unspecified, leaving a real gap at 0% coverage.

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?

States a specific verb and resource ('Allocate base and candidate VMs') and scopes it to a permitted local repository with uncommitted changes. The bare name 'start' carries little meaning on its own, and the description does not distinguish this tool from siblings like check, close, or compare.

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?

The phrase 'for a permitted local repository with uncommitted changes' functions as an implicit precondition for use, which is helpful. However, there is no explicit when-not guidance, no mention of the alternative to use if the repository has no uncommitted changes, and no statement about what to do after allocation (e.g., close).

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