Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

createTerminal

Destructive

Create a VS Code integrated terminal. Configure name, working directory, environment variables, and whether to show the terminal panel.

Instructions

Create VS Code integrated terminal. Options: name, cwd, env vars, shell.

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": "createTerminal"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking dir for terminal (must be within workspace)
envNoExtra env vars (key-value pairs, max 50 entries)
nameNoDisplay name for the terminal
showNoShow terminal panel after creation (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

The destructiveHint annotation suggests possible destructive behavior, but the description does not elaborate on implications (e.g., whether creation overwrites existing terminals). Adds no value beyond the annotation.

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

Conciseness3/5

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

Single sentence is concise but sacrifices clarity and accuracy. Could be improved by listing actual parameters or noting defaults.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 4 parameters, no output schema, and a minimal description, the tool lacks important context such as parameter defaults, constraints (cwd must be within workspace), and behavior on conflicts.

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

Parameters2/5

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

Schema covers 100% of parameters with descriptions. The description adds a misleading 'shell' option not in schema and omits the 'show' parameter, causing confusion about available 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?

Clearly states the tool creates a VS Code integrated terminal, distinguishing it from sibling tools like disposeTerminal and listTerminals. However, it inaccurately lists 'shell' as an option not present in the schema.

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 on when to use this tool vs alternatives (e.g., sendTerminalCommand, waitForTerminalOutput). Does not mention prerequisites or context for use.

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