Skip to main content
Glama

terminal_run

Destructive

Run controlled project commands such as Git checks, builds, tests, and linting, with explicit confirmation required for PowerShell scripts.

Instructions

Execute a controlled project command. PowerShell scripts need separate local opt-in and explicit confirmation.

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": {
      "project_path": "<project_path>",
      "action": "<action>"
    },
    "name": "terminal_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
scriptNo
confirmNo
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare this tool destructive, non-read-only, non-idempotent, and closed-world. The description adds a useful safety constraint for PowerShell scripts but does not otherwise explain execution scope, failure behavior, or what confirmation actually gates beyond that special case.

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?

The description is short, front-loaded, and free of filler. Its concision comes at the cost of missing operational detail, but structurally it is appropriately sized.

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?

For a destructive command-execution tool with four parameters, no output schema, and no parameter descriptions, the definition is substantially incomplete. The PowerShell note is useful but does not cover action values, project path expectations, confirmation semantics, or execution consequences.

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 description coverage is 0% and the description does not explain project_path, the action enum, script, or confirm. It only indirectly references the PowerShell action and confirmation requirement, leaving most parameter meaning undocumented.

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?

The description states a specific verb and scope: "Execute a controlled project command." It is clear that this runs project commands, but it does not differentiate itself from siblings such as terminal_plan or project_task_run.

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?

The only usage condition given is that PowerShell scripts require separate local opt-in and explicit confirmation. There is no general when-to-use guidance, no exclusions, and no comparison with alternative tools.

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