Skip to main content
Glama

devices

Lists simulated hardware, serial candidates, and BLE presets so you can identify available targets before using describe to handshake.

Instructions

List simulated devices, serial candidates and the BLE preset. Use describe to handshake.

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": "devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral context. It discloses the listing scope (simulated devices, serial candidates, BLE preset) and hints at a handshake follow-up with describe, but says nothing about permissions, output shape, pagination, or whether any side effects occur. For a simple zero-parameter listing tool this is adequate but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short, front-loaded sentences with no wasted words. The phrase 'Use describe to handshake' is terse and slightly jargon-heavy, but it still earns its place by pointing to the next action.

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 zero-parameter listing tool, the description gives the minimum viable context: what is listed and a pointer to describe for handshaking. But with no output schema and no annotations, it does not explain the return format or clarify what 'serial candidates' and 'BLE preset' mean, leaving gaps for an agent interpreting the results.

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 zero parameters, and schema coverage is effectively 100% because there is nothing to document. With no parameters to explain, the baseline is 4; the description has no parameter semantics to add or omit.

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 states a specific verb and resource set: 'List simulated devices, serial candidates and the BLE preset.' This is clearer than a tautology and tells an agent what data categories come back. It does not explicitly contrast with siblings like list_runs or read_parameters, so it stops short of a 5.

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

Usage Guidelines3/5

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

The line 'Use describe to handshake' gives one related next step, implying this tool is part of a discovery-to-handshake flow. However, it does not say when to use devices versus other sibling tools, nor does it state any exclusions or prerequisites. Usage is therefore implied rather than explicit.

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