Skip to main content
Glama
Sign In
AutoMobile

AutoMobile

by zillow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

terminateApp

Stop a mobile application by specifying its package ID to close running processes and free device resources.

Instructions

Terminate an app by package name

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": {
      "appId": "<appId>"
    },
    "name": "terminateApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp package ID of the app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Terminate' implies a destructive action, it doesn't specify whether this requires special permissions, what happens to app data, whether it's reversible, or potential side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at just 5 words, front-loading the essential information with zero wasted words. Every element ('Terminate', 'app', 'package name') earns its place in this efficient single-sentence structure.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address behavioral implications, return values, error conditions, or how it differs from similar tools. Given the complexity of app termination, more context is needed.

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?

The schema has 100% description coverage for its single parameter ('appId'), so the baseline is 3. The description adds no additional parameter information beyond what's already in the schema, maintaining this adequate but unenhanced level.

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 clearly states the action ('Terminate') and target resource ('an app by package name'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'killDevice' or 'launchApp' which also affect app/device state, so it doesn't reach the highest clarity level.

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 about when to use this tool versus alternatives like 'killDevice' or 'launchApp', nor about prerequisites or context. The description only states what the tool does, not when it's appropriate.

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