Skip to main content
Glama

stop_watching

Disable an app's network rule to restore normal traffic and stop monitoring it; choose a Mac app or an iOS Simulator app.

Instructions

Turn off an app's rule. Its traffic goes back to normal and stops being watched.

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

Input Schema

NameRequiredDescriptionDefault
appYesThe app: a bundle ID like com.me.MyApp, an app name, or * for every app in a simulator.
simulatorNoFor iOS Simulator apps: booted, any, a device name or a UDID. Leave out for a Mac app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the state transition — traffic returns to normal and watching ceases — but says nothing about whether the rule's captured data survives, whether the call is idempotent, or what happens if nothing is being watched. Useful effect disclosure, incomplete operational disclosure.

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?

Two short sentences, zero waste, with the action front-loaded and the effect immediately following. Nothing repeats the name or title verbatim for its own sake.

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?

The tool is simple (2 params, no output schema, no annotations), and the description covers the action and its effect. However, with no annotations and no output schema, an agent still lacks idempotency, error-condition, and return-value context — gaps the description could close in one clause.

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?

Schema coverage is 100%, so the schema already documents both 'app' (bundle ID, name, or *) and 'simulator' (booted/any/name/UDID). The description adds a small amount by framing the target as 'an app's rule', reinforcing that the identifier selects the rule's owner; the baseline for full coverage is 3, and the framing nudges it slightly above.

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 and resource: 'Turn off an app's rule', with the consequence that traffic reverts to normal. That contrasts implicitly with mutation siblings like fail_endpoint, mock_endpoint, and set_network, though it never names the counterpart tool that turns watching on.

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 implied by the effect ('stops being watched') rather than stated as a condition: an agent can infer this is the teardown for an active watch rule. There is no explicit when-to-use, no prerequisite (e.g., the app must currently be watched), and no named alternative such as reset_network.

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