Skip to main content
Glama
zillow
by zillow

checkPlatformDependencies

Verify installation status of required dependencies and tools for mobile platforms to ensure proper setup before automation tasks.

Instructions

Check the installation status of platform dependencies and tools

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesTarget platform to check dependencies for

Implementation Reference

  • The main handler function for the checkPlatformDependencies tool, dispatching to platform-specific check functions based on the input platform.
    const checkPlatformDependenciesHandler = async (args: CheckPlatformDependenciesArgs) => {
      try {
        if (args.platform === "android") {
          return await checkAndroidDependencies();
        } else if (args.platform === "ios") {
          return await checkIOSDependencies();
        } else {
          throw new ActionableError(`Unsupported platform: ${args.platform}`);
        }
      } catch (error) {
        throw new ActionableError(`Failed to check ${args.platform} dependencies: ${error}`);
      }
    };
  • Zod schema defining the input parameters for the checkPlatformDependencies tool (platform: android or ios).
    export const checkPlatformDependenciesSchema = z.object({
      platform: z.enum(["android", "ios"]).describe("Target platform to check dependencies for")
    });
  • Registration of the checkPlatformDependencies tool in the ToolRegistry, including name, description, schema, and handler.
    ToolRegistry.register(
      "checkPlatformDependencies",
      "Check the installation status of platform dependencies and tools",
      checkPlatformDependenciesSchema,
      checkPlatformDependenciesHandler
    );
  • Helper function that implements the actual Android dependency checking logic called by the main handler.
    async function checkAndroidDependencies(): Promise<any> {
      logger.info("Checking Android dependencies status");
    
      const status = await getInstallationStatus();
      const javaStatus = await checkJavaInstallation();
    
      return createJSONToolResponse({
        platform: "android",
        hasInstallation: status.hasInstallation,
        locations: status.locations,
        bestLocation: status.bestLocation,
        recommendations: status.recommendations,
        availableTools: status.bestLocation?.available_tools || [],
        installationPath: status.bestLocation?.path || null,
        installationSource: status.bestLocation?.source || null,
        version: status.bestLocation?.version || null,
        java: {
          installed: javaStatus.installed,
          version: javaStatus.version,
          javaHome: javaStatus.javaHome
        }
      });
    }
  • Helper function providing a stub implementation for iOS dependency checking.
    async function checkIOSDependencies(): Promise<any> {
      logger.info("Checking iOS dependencies status (stub)");
    
      return createJSONToolResponse({
        platform: "ios",
        hasInstallation: false,
        message: "iOS dependency checking is not yet implemented",
        recommendations: [
          "iOS support is planned for a future release",
          "Manually verify Xcode is installed",
          "Check that iOS Simulator is available"
        ]
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'check' implies a read-only diagnostic operation, the description doesn't clarify what 'installation status' means (e.g., returns boolean, list of missing dependencies, detailed report), whether it has side effects, or what permissions/context it requires. This leaves significant behavioral uncertainty.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple diagnostic tool and front-loads the core functionality.

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?

For a simple diagnostic tool with one well-documented parameter and no output schema, the description is minimally adequate. However, it lacks important context about what the check returns (status format, error conditions) and how it relates to the sibling 'installPlatformDependencies' tool, which reduces completeness for practical agent usage.

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%, with the single parameter 'platform' clearly documented in the schema as a required enum with values 'android' or 'ios'. The description adds no additional parameter semantics beyond what the schema already provides, which meets the baseline expectation when schema coverage is high.

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 verb ('check') and resource ('installation status of platform dependencies and tools'), making the purpose understandable. However, it doesn't explicitly differentiate from the sibling tool 'installPlatformDependencies', which could create ambiguity about when to use each tool.

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?

The description provides no guidance on when to use this tool versus alternatives. With a sibling tool named 'installPlatformDependencies', there's a clear related alternative, but the description doesn't mention it or provide any context about prerequisites, timing, or workflow sequencing.

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