Skip to main content
Glama

List Developer and Consumer runner clients

list_runner_clients
Read-only

Lists dashboard-owned Developer Runner clients separately from Consumer App Runners, avoiding runner-type inference from missing or present device IDs.

Instructions

Lists the dashboard-owned Developer Runner separately from Consumer App Runners. Use this instead of inferring runner kind from a missing or present device id.

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_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalRBlockIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the useful behavioral detail that Developer and Consumer runner clients are returned separately, but it does not explain return shape, permissions, or the required identifier.

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?

Two compact sentences, with the core listing behavior front-loaded. The second sentence is somewhat cryptic but still earns its place by giving a usage heuristic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with one required but undocumented parameter and no output schema, the description leaves an agent without a clear explanation of the identifier or what the response will contain. It covers purpose and one usage heuristic, but not enough for confident invocation.

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 single required parameter, signalRBlockId, has 0% schema description coverage, and the description never mentions it. Because there is only one parameter this is not the worst case, but the description provides no compensating meaning for what the identifier represents.

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: it lists Developer Runner clients separately from Consumer App Runner clients. It does not explicitly differentiate itself from siblings such as list_runner_devices, but the developer-vs-consumer scoping is clear.

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?

It gives one useful usage cue: use this rather than inferring runner kind from device-id presence or absence. It does not name alternative tools or state when this tool should not be used.

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