Skip to main content
Glama

Terminate App

terminate_app
DestructiveIdempotent

Terminates an owned application process and closes idle virtual windows, keeping your Wayland desktop clean and freeing resources.

Instructions

Terminates an owned application process and closes idle virtual windows.

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

Input Schema

NameRequiredDescriptionDefault
pidNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is covered. The description adds real value with the "owned" scope restriction and the window-closing consequence, but is silent on the most consequential question: what happens when the optional pid is omitted.

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?

One tight sentence, front-loaded with the action and its blast radius. No filler, though the terseness comes at the cost of the missing parameter behavior.

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?

An output schema exists, so return values need not be explained, and annotations carry the destructive/idempotent signals. However, for a destructive single-param tool where the param is optional and undocumented, the description leaves an agent unable to predict scope of destruction.

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% for the single parameter pid, and the description says nothing about it — not its meaning, not whether null/omitted targets all owned apps or fails. For a destructive tool this is a meaningful gap the description should have closed.

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?

Specific verb+resource ("Terminates an owned application process") plus a stated side effect ("closes idle virtual windows"). It is distinguishable from launch_app/restart_app by intent, though it never names those siblings explicitly.

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 only implied — an agent can infer this is the kill-switch when a process must be stopped. There is no explicit guidance on when to pick this over restart_app or window_control, and no stated preconditions.

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