Skip to main content
Glama

list_device_models

Read-only

Lists available device models with OS, platform, form factor, and free or busy counts so you can pick a model for dev_start; models with none free queue until one opens.

Instructions

List the device models you can start right now (model, OS version, platform, category, form_factor "foldable" for any device with a hinge — the iPhone Duo, Android foldables such as the Pixel 9 Pro Fold — and how many of each are free and busy). Pass a model name to dev_start to run on it; a model with none free queues until one is.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_device_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_typeNoOnly models of this device type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real value by explaining that each row includes free/busy capacity counts and that a model with zero free slots causes queuing rather than failure. It does not mention whether the list is paginated or how large it typically is, so it stops short of fully rich behavioral 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 purpose is front-loaded in the first clause and the parenthetical packs the return-field inventory without redundancy. The second sentence covers the follow-up action and queuing edge case in minimal words.

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?

With no output schema, the description carries the burden of describing return content and does so by naming model, OS version, platform, category, form factor and availability counts. Only minor gaps remain, such as whether results are ordered or truncated; the foldable example ("iPhone Duo") is slightly questionable but does not impair correct invocation.

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 coverage is 100% and the single device_type enum is fully documented in the schema, so the baseline is 3. The description never references device_type or how filtering interacts with the foldable categorization, so it adds no meaning beyond the schema.

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?

States a specific verb and resource ("List the device models") plus the operational scope ("you can start right now") and enumerates the returned fields, so an agent can distinguish it from siblings like list_apps or dev_start immediately.

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

Usage Guidelines4/5

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

Explicitly routes the agent forward: take a model name from this list and pass it to dev_start, and explains the queueing consequence when nothing is free. That covers the positive path well, but there is no explicit statement of when not to call it or of a filtering alternative.

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