Skip to main content
Glama

Revoke every Consumer App Runner

revoke_all_consumer_runners
Destructive

Revoke and disconnect all Consumer App Runners on a specified block to prevent unauthorized access, leaving the Developer Runner unaffected. Confirmation is required.

Instructions

Revokes and disconnects every Consumer App Runner enrolled on the block. The Developer Runner is 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_all_consumer_runners"
  }
}

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?

Annotations already declare destructiveHint=true, so the destructive nature is known; the description adds real value on top by disclosing the concrete effect (runners are revoked AND disconnected), the blast radius (all consumer runners on the block), the deliberate exclusion of the Developer Runner, and the confirm gate. It does not say whether runners can re-enroll or how in-flight work is handled, which keeps it below a 5.

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, front-loaded with the action and scope, followed by the exclusion and then the precondition. No repetition of the title or name and no filler.

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 destructive bulk operation with no output schema and two parameters, the definition covers effect, scope, exclusion, and the confirm requirement — enough to call it safely. Minor gaps remain around reversibility and post-revocation state of affected runners.

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 carries the burden. It fully explains the meaning of 'confirm' as a required safety gate, and 'on the block' implicitly scopes signalRBlockId, but that parameter is never named or described, leaving one of two parameters unaddressed.

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?

States a specific verb ('Revokes and disconnects'), a precise resource ('every Consumer App Runner enrolled on the block') and a scope qualifier ('every'), then explicitly carves out the Developer Runner as unaffected. That exclusion lets an agent distinguish this from the sibling revoke_developer_runner without opening either 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?

Gives clear selection context: use it for the bulk consumer-runner case, not the Developer Runner, and a hard precondition ('Requires confirm:true'). It stops short of naming a single-runner alternative or stating when not to use a bulk revoke at all, so it is strong but not exhaustive.

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