Skip to main content
Glama

Execute on one enrolled runner device

execute_runner_device

Executes a runner block by signalR block ID on exactly one authorized device, resolving deviceId server-side instead of trusting browser input.

Instructions

Targets exactly one device. The application backend must resolve deviceId from its authenticated user mapping; never accept an arbitrary browser-supplied device id as authorization.

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>",
      "deviceId": "<deviceId>"
    },
    "name": "execute_runner_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNo
deviceIdYes
signalRBlockIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It contributes one genuinely useful disclosure — that deviceId must come from the backend's authenticated user mapping and never from a browser-supplied value — but says nothing about side effects, whether execution is destructive, whether it blocks, or what failure looks like.

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 short sentences, front-loaded with the scope constraint followed by the security rule, with no filler. The issue is under-specification rather than verbosity.

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 three-parameter execution tool with no annotations and no output schema, the description leaves the core action, the signalRBlockId parameter, and all behavioral consequences undocumented. The authorization note is valuable but far from sufficient.

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?

Schema description coverage is 0% across three parameters. The description adds meaning only for deviceId (its trust/sourcing rule); signalRBlockId and the input object remain completely unexplained, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the targeting scope ("Targets exactly one device") but never says what is actually executed or what signalRBlockId represents; the action itself is only inferable from the name and title. It does distinguish this from broadcast/multi-device siblings by emphasizing single-device scope, which is real added value.

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?

There is no when-to-use guidance and no comparison to related execution tools such as execute_sql or execute_workspace, which are the obvious alternatives an agent would weigh. The only guidance given is an authorization constraint, not a selection criterion.

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