Skip to main content
Glama

iphone_stop_agent

Idempotent

Stops WebDriverAgent on the iPhone and closes the automation connection when a session ends, leaving apps and data untouched; other iphone tools stay unavailable until the agent is started again.

Instructions

Stop WebDriverAgent on the iPhone and close the connection.

Use it when the session is finished, so the automation port on the phone is no longer open. Afterwards
every other iphone_* tool fails until iphone_start_agent is called again. Leaves apps and data untouched.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description goes beyond them by disclosing the downstream consequence (every other iphone_* tool fails until restart) and the blast radius ("Leaves apps and data untouched"). That is exactly the kind of context annotations cannot express. It stops short of describing failure behavior when the agent is not already running, so it is not a full 5.

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?

Three short sentences, each carrying a distinct fact: what it does, when to use it, and what stops working afterwards. Front-loaded with the action and zero redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers purpose, timing and side effects thoroughly. The only gap is the error case (calling it when no agent is running), which matters slightly given the idempotent hint but is a minor omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, and the schema is fully described, so there is no parameter meaning the description needs to supply. Baseline 4 applies for a zero-parameter tool.

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 opens with a specific verb and resource ("Stop WebDriverAgent on the iPhone and close the connection"), which precisely names the action and its immediate effect. It is unmistakably distinct from iphone_start_agent and the other iphone_* helpers, which all operate on the live session this tool tears down.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use it when the session is finished" gives an explicit trigger condition, and the follow-on sentence names the alternative (iphone_start_agent) and the state that requires it. An agent knows both when to call this and why it would need to reverse it.

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