Skip to main content
Glama

tauri_list_devices

Read-only

List Android emulators/devices and iOS simulators for Tauri mobile development. Use this tool to identify available testing targets when building Tauri mobile applications.

Instructions

[Tauri Mobile Apps Only] List Android emulators/devices and iOS simulators. Use for Tauri mobile development (tauri android dev, tauri ios dev). Not needed for desktop-only Tauri apps or web projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of device listing: fetches Android devices using 'adb devices -l' and iOS booted simulators using 'xcrun simctl list devices booted', handling errors gracefully.
    export async function listDevices(): Promise<{ android: string[]; ios: string[] }> {
       const [ android, ios ] = await Promise.all([
          getAndroidDevices(),
          getIOSSimulators(),
       ]);
    
       return { android, ios };
    }
  • Zod schema for tauri_list_devices input parameters (empty object, no params required).
    export const ListDevicesSchema = z.object({});
  • Tool registration in the central TOOLS registry, defining metadata, schema, annotations, and thin wrapper handler that calls listDevices() and formats output as text.
    {
       name: 'tauri_list_devices',
       description:
          '[Tauri Mobile Apps Only] List Android emulators/devices and iOS simulators. ' +
          'Use for Tauri mobile development (tauri android dev, tauri ios dev). ' +
          'Not needed for desktop-only Tauri apps or web projects.',
       category: TOOL_CATEGORIES.MOBILE_DEVELOPMENT,
       schema: ListDevicesSchema,
       annotations: {
          title: 'List Mobile Devices',
          readOnlyHint: true,
          openWorldHint: false,
       },
       handler: async () => {
          const devices = await listDevices();
    
          return `Android Devices:\n${devices.android.join('\n') || 'None'}\n\niOS Booted Simulators:\n${devices.ios.join('\n') || 'None'}`;
       },
    },
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, indicating a safe, bounded operation. The description adds valuable context about the tool's scope (mobile-only, Tauri-specific) and development use case, which goes beyond what annotations provide. No contradictions with annotations exist.

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 front-loaded with the core purpose in the first sentence, followed by usage guidance. Both sentences earn their place by providing essential information without redundancy. It's efficiently structured and appropriately sized for the tool's complexity.

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?

Given the tool has no parameters, annotations cover safety and scope hints, and no output schema exists, the description provides good contextual completeness. It explains the tool's purpose, usage boundaries, and development context. A slight gap exists in not detailing the return format (e.g., list structure), but this is mitigated by the tool's simplicity.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters, as none exist, and instead focuses on the tool's purpose and usage context, which is the correct approach for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific verb ('List') and resources ('Android emulators/devices and iOS simulators'), and explicitly distinguishes this tool from sibling tools by specifying it's for mobile development only and not needed for desktop-only Tauri apps or web projects. The purpose is specific and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool ('for Tauri mobile development') and when not to use it ('Not needed for desktop-only Tauri apps or web projects'). It clearly defines the appropriate context and exclusions, helping the agent choose this tool versus alternatives.

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/hypothesi/mcp-server-tauri'

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