Skip to main content
Glama
Sign In
antigravity-terminal-mcp

antigravity-terminal-mcp

by aathishwar-13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kill_command

Terminate a running Windows terminal command by command ID to free stuck sessions. Stop persistent PowerShell or VS Code processes for full control.

Instructions

Terminate a running command by command_id.

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": {
      "command_id": "<command_id>"
    },
    "name": "kill_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely restates the action (terminate) without providing any additional context about the effect on the process, reversibility, error handling, or session state.

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?

The description is a single focused sentence, concise and front-loaded with the verb. Every word is necessary and there is no fluff.

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 simple one-parameter tool, the description provides the essential purpose but omits behavioral details like return values, error scenarios, or relationship to sibling tools. Given no annotations or output schema, a bit more context would be helpful, but the tool's simplicity keeps it at a minimum viable level.

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?

The description mentions 'by command_id' but adds minimal meaning beyond the schema's property name. It does not explain what command_id represents, how to obtain it, or any expected format. Given 0% schema coverage, this is insufficient.

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?

The description states 'Terminate a running command by command_id,' which uses a specific verb ('terminate') and resource ('running command'). It clearly distinguishes the tool from siblings like run_command, command_status, and send_input, while identifying the key parameter.

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 is provided on when to use this tool vs. alternatives. The description only states the core purpose and does not mention any exclusions, prerequisites, or references to sibling tools.

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