Skip to main content
Glama

Revoke one runner device

revoke_runner_device

Revoke a selected runner device after confirmation; the action targets only that device and does not affect other users' runners.

Instructions

Revokes only the selected device. Requires confirm:true and does not affect other users' runners.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
deviceIdYes
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?

With no annotations, the description carries the full burden. It usefully discloses the confirm:true precondition and the blast radius (other users' runners unaffected), but says nothing about irreversibility, permissions or auth requirements, or what happens to a revoked device.

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, no filler, with the scope constraint front-loaded and the precondition second. Very little waste, though it is arguably too terse for a destructive operation.

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?

A destructive, unannotated mutation with a required parameter whose meaning is undocumented and no output schema. The description covers safety scoping and the confirm gate but leaves the agent without enough to correctly supply signalRBlockId or predict the result.

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, and the description only explains confirm. deviceId is inferable from the title, but signalRBlockId — a required parameter — is entirely opaque in both schema and description, leaving the caller to guess its format and source.

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?

States a specific verb and resource ("Revokes only the selected device") and scopes it against the bulk sibling by saying it does not affect other users' runners. It stops short of naming a specific alternative tool, but the single-device scope is unambiguous.

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?

Implicit routing is present: use this for a single device rather than a bulk revoke, plus the prerequisite that confirm must be true. There is no explicit when-not clause, no named sibling alternative, and no statement of what state the device must be in before revocation.

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