Skip to main content
Glama

desktop_close_app

Quit an application gracefully, or force-terminate matching processes to close unresponsive apps.

Instructions

agent-desktop close-app: Quit an application gracefully (--force to terminate)

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": {
      "app": "<app>"
    },
    "name": "desktop_close_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesApplication name
forceNoTerminate matching app processes instead of quitting gracefully

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It signals that closing is graceful by default, but says nothing about unsaved-work loss, whether all instances are affected, permission requirements, or what happens if the app is not running — critical for a terminating operation.

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?

A single tight line with the action front-loaded after the tool prefix. The '--force' CLI-style notation is slightly ambiguous next to a boolean parameter, but nothing is wasted.

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 no annotations and no output schema, the description should disclose what a destructive terminate entails — data-loss risk, scope, and outcome. It covers only the graceful/forced distinction, which the schema already provides, leaving the agent under-informed for a quit/terminate action.

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 100%, so both parameters, including the force/graceful distinction, are already documented. The description restates the force semantics in shorthand ('--force') without adding format, defaults, or behavior beyond the schema.

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 plus resource ('Quit an application') and contrasts graceful quitting with forced termination, so it is clearly the inverse of launch-type siblings. It stops short of naming a sibling or a boundary case 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 by the verb — an agent can infer it should call this to shut an app down, but there is no guidance on when to prefer graceful vs force, no prerequisites, and no mention of any related tool for relaunching or verifying state.

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