Skip to main content
Glama
Sign In
Manos MCP

Manos MCP

by ryanperkins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Stop app

stop_app

Terminate a running app on a specified Android or iOS device by providing the device ID and app ID.

Instructions

Force-stop / terminate an app.

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": {
      "device_id": "<device_id>",
      "app_id": "<app_id>"
    },
    "name": "stop_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
device_idYesDevice id from list_devices (adb serial like 'emulator-5554', or an iOS simulator UDID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'Force-stop' implies abrupt termination, but it does not mention effects on app data, unsaved state, or required permissions. No return value or side effects are described.

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 a single, focused phrase with no filler. It front-loads the core action, though it sacrifices useful context for brevity.

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?

The description is minimal, covering only the basic action. Without usage guidance or annotations, an agent cannot confidently choose this tool over siblings like clear_app_state or launch_app. The simple nature of the tool slightly mitigates but does not resolve the gaps.

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 coverage is 50%: device_id has a helpful description, but app_id is undocumented. The description adds no parameter-level helpfulness beyond implying that app_id identifies the app to stop.

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 uses specific verbs 'Force-stop/terminate' and identifies resource 'an app', making the action unambiguous. It does not explicitly distinguish from siblings like clear_app_state or launch_app, but the core purpose is clear.

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 versus alternatives. It does not mention prerequisites, exclusions, or related operations such as clearing app state or launching an app.

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