Skip to main content
Glama

reset_network

Restore normal network speed and clear failures, host limits, or endpoint rules for a Mac or iOS Simulator app while keeping its requests monitored.

Instructions

Put an app back to full speed with no failures, host limits or endpoint rules. It stays watched, so its requests still show.

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

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.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses exactly what state is cleared (failures, host limits, endpoint rules) and, importantly, that watching continues afterward, so the agent knows not to re-initiate monitoring. It stops short of saying whether mocked endpoints or other state survive the reset.

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 tight sentences: the effect is front-loaded and the state-persistence note follows. No filler or redundant restatement of the name.

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?

For a two-parameter state-mutating tool with no annotations or output schema, the description covers the action and the key side effect (watching persists) well. It could more explicitly state whether mocks/endpoints are also cleared, but the essentials for correct invocation are present.

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 coverage is 100%, so both the app and simulator parameters are already fully documented in the schema, including the '*' wildcard and UDID options. The description adds no parameter meaning beyond that baseline.

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 states a concrete action and its effects: it removes failures, host limits, and endpoint rules for an app. However, it never uses the word 'reset' in a way that distinguishes it from clear_endpoints or set_network, so sibling differentiation relies on inference.

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?

There is no explicit 'use this when...' guidance or named alternative. The sentence 'It stays watched, so its requests still show' implies the usage context for restoring normal traffic, but which tool to pick over clear_endpoints or set_network is left implicit.

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