Skip to main content
Glama

reset_network_condition

Reset network conditions to default in a simulator for testing network-dependent applications.

Instructions

Resets network conditions to default in the simulator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
simulatorUuidYesUUID of the simulator to use (obtained from list_simulators)

Implementation Reference

  • The async handler function for the 'reset_network_condition' tool. It logs the action and calls executeSimctlCommandAndRespond to run the simctl command 'status_bar [uuid] clear' which resets the network conditions (and status bar) on the simulator.
    async (params: { simulatorUuid: string }): Promise<ToolResponse> => {
      log('info', `Resetting simulator ${params.simulatorUuid} network condition`);
    
      return executeSimctlCommandAndRespond(
        params,
        ['status_bar', params.simulatorUuid, 'clear'],
        'Reset Network Condition',
        `Successfully reset simulator ${params.simulatorUuid} network conditions.`,
        'Failed to reset network condition',
        'reset network condition',
      );
    },
  • Zod input schema defining the simulatorUuid parameter for the tool.
      simulatorUuid: z
        .string()
        .describe('UUID of the simulator to use (obtained from list_simulators)'),
    },
  • The registerResetNetworkConditionTool function that registers the tool on the MCP server, providing name, description, input schema, and handler.
    export function registerResetNetworkConditionTool(server: McpServer): void {
      server.tool(
        'reset_network_condition',
        'Resets network conditions to default in the simulator.',
        {
          simulatorUuid: z
            .string()
            .describe('UUID of the simulator to use (obtained from list_simulators)'),
        },
        async (params: { simulatorUuid: string }): Promise<ToolResponse> => {
          log('info', `Resetting simulator ${params.simulatorUuid} network condition`);
    
          return executeSimctlCommandAndRespond(
            params,
            ['status_bar', params.simulatorUuid, 'clear'],
            'Reset Network Condition',
            `Successfully reset simulator ${params.simulatorUuid} network conditions.`,
            'Failed to reset network condition',
            'reset network condition',
          );
        },
      );
    }
  • Configuration object in toolRegistrations array that enables conditional registration of the reset_network_condition tool based on environment variable.
      register: registerResetNetworkConditionTool,
      groups: [ToolGroup.SIMULATOR_MANAGEMENT],
      envVar: 'XCODEBUILDMCP_TOOL_RESET_NETWORK_CONDITION',
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Resets') but doesn't clarify if this is a destructive operation, what 'default' means specifically, whether it requires specific permissions, or what the outcome looks like (e.g., success confirmation). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core action and target without unnecessary words. It's appropriately sized for a simple tool, with zero waste or redundancy, making it easy for an agent to parse quickly.

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?

Given the tool's mutation nature (resetting implies change) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral aspects like safety, permissions, or result format, leaving gaps for the agent. While concise, it fails to provide enough context for reliable use in a simulator management environment.

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 input schema has 100% description coverage, with the single parameter 'simulatorUuid' documented as 'UUID of the simulator to use (obtained from list_simulators)'. The description doesn't add any meaning beyond this, as it doesn't mention parameters at all. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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 ('Resets') and target ('network conditions to default in the simulator'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'set_network_condition', but the verb 'resets' implies a distinct operation from 'set', so it's not vague. It avoids tautology by specifying what gets reset beyond just the name.

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 like 'set_network_condition' or other simulator management tools. The description implies usage for resetting network conditions, but lacks explicit context, prerequisites (e.g., after using 'set_network_condition'), or exclusions. This leaves the agent without clear direction on appropriate scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SampsonKY/XcodeBuildMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server