Skip to main content
Glama
andreahaku

Expo iOS Development MCP Server

by andreahaku

detox.healthcheck

Verify Detox session readiness for UI automation testing in Expo iOS development environments.

Instructions

Check if Detox session is ready

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the "detox.healthcheck" MCP tool. The inline handler fetches the result from healthCheck() in detox/runner.ts and formats it as MCP response.
    server.tool(
      "detox.healthcheck",
      "Check if Detox session is ready",
      {},
      async () => {
        try {
          const result = await healthCheck();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2),
              },
            ],
          };
        } catch (error) {
          return handleToolError(error);
        }
      }
    );
  • Core implementation of the healthcheck: checks if Detox state is 'ready' by querying the global state manager.
    export async function healthCheck(): Promise<{
      ready: boolean;
      state: string;
      sessionId?: string;
    }> {
      const detoxState = stateManager.getDetox();
    
      return {
        ready: detoxState.state === "ready",
        state: detoxState.state,
        sessionId: detoxState.sessionId,
      };
    }
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 tool checks readiness but doesn't explain what 'ready' means, whether it's a read-only operation, what happens if the session isn't ready, or any error conditions. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently communicates the essential function without unnecessary elaboration, 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 complexity of session management and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'ready' entails, what the return value indicates, or how it integrates with sibling tools like 'detox.session.start' and 'detox.session.stop', leaving the agent with insufficient context for effective use.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, and since there are none, it doesn't need to compensate for any gaps, earning a baseline score above 3.

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 tool's purpose as 'Check if Detox session is ready' with a specific verb ('Check') and resource ('Detox session'), making it immediately understandable. However, it doesn't distinguish itself from potential alternatives like 'expo.status' or clarify what constitutes 'ready' versus other session states.

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. It doesn't mention prerequisites (e.g., after starting a session), exclusions, or how it differs from sibling tools like 'detox.session.start' or 'expo.status', leaving the agent to infer usage context.

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/andreahaku/expo_ios_development_mcp'

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