Skip to main content
Glama

Read devices

AccountDevicesReadTool
Read-onlyIdempotent

The account's devices: list them, read one, and read its logs, an upcoming check-in forecast, its playlist coverage or its timeline (what it showed today and what it will show next).

  • listDevices: List my devices

  • getDevice: Get the data of a device — params: id (path)

  • getDeviceLogs: Read the logs of a device — params: device_id (path), level (query: one of debug, info, warn, error), source (query: one of device, plugin, custom_plugin, private_plugin, mashup, support), limit (query), before_ts (query), before_event_id (query)

  • getDeviceForecast: Simulate a device's coming check-ins, deciding each one the way a real check-in would — params: device_id (path), hours (query)

  • getDevicePlaylistCoverage: Times of the week a device's playlist shows nothing scheduled — params: device_id (path)

  • getDeviceTimeline: Read a device timeline — params: device_id (path), date (query), source (query), hours (query: one of 3, 12, 24)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "AccountDevicesReadTool"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe API operation to run
paramsNoThe operation's path, query and body parameters by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral substance beyond that: forecast 'decides each one the way a real check-in would' (i.e. a simulation, not a persisted check-in) and playlist coverage returns unscheduled time slots. It stays silent on result shape and any pagination semantics for listDevices/getDevice, which keeps it from a 5.

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?

Front-loaded summary sentence establishes scope, then one bullet per sub-action with params inline — no filler and no repetition. Density is high but every clause carries an operation name or a parameter fact the agent needs.

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?

No output schema exists, and the description partially compensates by explaining what timeline and playlist-coverage results mean, but it says nothing about the shape of listDevices or getDevice responses. With annotations fully covering the safety profile and parameters thoroughly enumerated, this is close to complete for a multiplexed read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only exposes a free-form 'params' object, so the description carries the real burden — and it delivers by listing each operation's parameter names, marking path vs query, and enumerating accepted values for level, source, and hours. The only remaining gaps are formats for date, before_ts, and before_event_id, which is minor against how much it adds over 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?

The opening sentence names the resource (the account's devices) and states the specific verbs the tool supports, then enumerates all six sub-operations so the agent knows the full action surface without opening the schema. Each sub-action is stated as a concrete verb+resource pair (list devices, get device logs, simulate check-ins, read playlist coverage, read timeline), which is far more specific than the generic tool name.

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?

Each sub-action carries enough context to know when it applies — e.g. 'Simulate a device's coming check-ins' for forecast versus 'what it showed today and what it will show next' for timeline. It does not, however, name sibling tools (AccountDevicesWriteTool, AccountAppsReadTool) or state exclusions, so the agent must infer from the resource name that writes belong elsewhere.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources