Skip to main content
Glama

List enrolled runner devices

list_runner_devices
Read-only

Lists independently enrolled devices for a specified SignalR block, showing live connection status, revoked state, and last connection time.

Instructions

Lists independently enrolled devices, with connected=true/false for live presence or null when the Executor is unavailable, plus revoked and last-connected state.

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": {
      "signalRBlockId": "<signalRBlockId>"
    },
    "name": "list_runner_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalRBlockIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

B3.2/5.0
Behavior4/5

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

The readOnlyHint=true annotation already establishes that this is a safe read, but the description adds a genuine runtime trait: the connected field is true or false for live presence, or null when the Executor is unavailable. That degraded-state disclosure is useful context the annotations do not carry, although the description does not say whether revoked devices are included in the results or whether results are paginated.

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?

Everything is packed into a single front-loaded sentence with no filler, and the return-value semantics are stated compactly. The sentence is dense, but every clause adds information.

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?

Because there is no output schema, the description must explain the return shape itself, and it partially does by covering connected, revoked, and last-connected state. It omits the meaning of the required signalRBlockId parameter and says nothing about result volume, pagination, or ordering, which leaves meaningful gaps for a listing tool with an undocumented required parameter.

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

Parameters2/5

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

The schema description coverage is 0% for the single required parameter, signalRBlockId, so the description must carry the full burden of explaining it, and it says nothing about it. The agent cannot tell whether the ID scopes the results to a workspace, a domain, or a runner block.

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 uses a specific verb and resource ('Lists independently enrolled devices') and the qualifier 'independently enrolled' implicitly separates it from list_runner_clients. However, no sibling is named explicitly, so the agent must infer the distinction from the sibling name alone.

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 gives no when-to-use or when-not-to-use guidance, and it never points to related tools such as rename_runner_device or revoke_runner_device for follow-up actions. The agent can only infer that this is an inspection tool from the word 'Lists'.

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