Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

disable_automation

DestructiveIdempotent

Stops an automation from running on new events; already queued runs finish. Confirm with the user before disabling.

Instructions

Switch an automation off: it stops running on new events (runs already queued finish). Confirm with the user first.

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": {
      "automation": "<automation>"
    },
    "name": "disable_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
automationYesthe automation's id or name

Output Schema

NameRequiredDescriptionDefault
nextYeswhat to do next
automationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description still adds real value by scoping the destruction ('runs already queued finish'), which tells the agent this is not an abort of in-flight work. The user-confirmation requirement is additional behavioral context not present in the annotations.

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?

Two short sentences, zero filler. The effect is front-loaded and the confirmation caveat follows, which is the right order for an agent to read.

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

Completeness5/5

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

For a one-parameter mutation with an output schema present, nothing material is missing: effect scope, idempotency, destructiveness, and the confirmation step are all covered. Return values need not be explained given the output schema.

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 100% and the single parameter already documents that it accepts an id or name. The description adds no further meaning about the identifier, so the baseline of 3 applies.

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 ('Switch an automation off') and immediately defines the effect: it stops running on new events. That is precise enough to distinguish it from enable_automation or delete-style operations without opening a schema. It stops just short of naming a sibling or contrasting with a delete/pause alternative.

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 an explicit procedural precondition — 'Confirm with the user first' — which is exactly the kind of when-to-use guidance a mutating tool needs. It does not state when NOT to use it (e.g., versus a full delete or update_automation), so the guidance is clear but not exhaustive.

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