Skip to main content
Glama
zillow
by zillow

disableDemoMode

Turn off demo mode on Android or iOS devices to restore standard status bar functionality for testing and automation workflows.

Instructions

Disable demo mode and return to normal status bar behavior

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesTarget platform

Implementation Reference

  • Implements the execution logic for the disableDemoMode tool. Creates a DemoMode instance for the booted device, calls exitDemoMode(), handles the result or errors, and returns a JSON tool response.
    const disableDemoModeHandler = async (device: BootedDevice) => {
      try {
        const demoMode = new DemoMode(device);
        const result = await demoMode.exitDemoMode();
    
        return createJSONToolResponse({
          message: "Demo mode disabled",
          observation: result.observation,
          ...result,
          demoModeEnabled: false
        });
      } catch (error) {
        logger.error("Failed to disable demo mode:", error);
        throw new ActionableError(`Failed to disable demo mode: ${error}`);
      }
    };
  • Zod schema for validating input parameters of the disableDemoMode tool, which requires a 'platform' field.
    export const disableDemoModeSchema = z.object({
      platform: z.enum(["android", "ios"]).describe("Target platform")
    });
  • Registers the disableDemoMode tool in the ToolRegistry using registerDeviceAware, providing the tool name, description, input schema, and handler function.
    ToolRegistry.registerDeviceAware(
      "disableDemoMode",
      "Disable demo mode and return to normal status bar behavior",
      disableDemoModeSchema,
      disableDemoModeHandler
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the action and outcome but doesn't address important behavioral aspects like whether this requires specific permissions, if it's reversible, what happens to existing demo mode settings, or potential side effects. The description is minimal and lacks operational context.

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 extremely concise - a single sentence that directly states the tool's purpose. There's zero wasted language, and it's front-loaded with the core action. Every word earns its place in this minimal description.

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?

For a tool that presumably changes system behavior (disabling demo mode), the description is inadequate given no annotations and no output schema. It doesn't explain what 'demo mode' is, what 'normal status bar behavior' means, or what the tool returns. The minimal description leaves too many contextual gaps for effective agent use.

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 description coverage is 100%, so the schema already documents the single 'platform' parameter with its enum values. The description doesn't add any parameter-specific information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 ('Disable demo mode') and the outcome ('return to normal status bar behavior'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'enableDemoMode' beyond the obvious opposite action, which prevents a perfect score.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, timing considerations, or what 'demo mode' represents in context. It simply states what the tool does without contextual usage information.

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/zillow/auto-mobile'

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