Skip to main content
Glama

Revoke the Developer Runner

revoke_developer_runner
Destructive

Revoke a dashboard-owned Developer Runner and disconnect it immediately. This action leaves Consumer App Runners unaffected and requires confirm:true.

Instructions

Revokes the dashboard-owned Developer Runner and disconnects it immediately. Consumer App Runners are deliberately unaffected. Requires confirm:true.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
signalRBlockIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.2/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description still adds real value: the disconnection is immediate (no grace period), the blast radius is explicitly limited to the dashboard-owned Developer Runner, and a confirmation flag gates the action. It doesn't cover failure modes (e.g., unknown block id) or permission requirements.

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?

Three short sentences, action first, scope next, precondition last. No filler and nothing buried.

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?

For a two-parameter destructive call with no output schema and only a destructiveHint annotation, the description covers effect, immediacy, scope, and the confirmation gate. The remaining gap is the identity/format of signalRBlockId and any authorization requirement, which matters when the tool is irreversible.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It correctly signals that confirm must be true to proceed, but signalRBlockId — the sole required parameter — is never explained, so the agent must guess that it identifies the runner to revoke.

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?

"Revokes the dashboard-owned Developer Runner and disconnects it immediately" gives a specific verb plus a precisely scoped resource, and the second sentence carves out Consumer App Runners so the agent can distinguish this from sibling revoke_all_consumer_runners / revoke_runner_device without opening any schema.

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?

The exclusion "Consumer App Runners are deliberately unaffected" tells the agent when this tool is the wrong choice, and "Requires confirm:true" gives a precondition for a successful call. It stops short of naming which sibling to use for consumer runners, so the alternative is inferred rather than stated.

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