Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

enable_automation

DestructiveIdempotent

Activates an existing automation so it runs on every trigger event and applies its license changes and customer messages; use only after a successful test run and with required permissions.

Instructions

Switch an automation on: from then on it runs on every trigger event and its actions change real licenses and message real customers. Only when the user asked for it, after a test run; it must have no problems, and the member needs the permissions its actions use.

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": "enable_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
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's real contribution is the concrete blast radius: real licenses change and real customers get messaged, plus an authorization prerequisite. It does not say what happens if the automation is already on, despite idempotentHint=true, nor how to verify "no problems", which leaves a small gap.

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?

One front-loaded sentence covering effect, precondition and permission, with no filler. The semicolon-chained clauses and the vague "it must have no problems" cost a little precision.

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?

An output schema exists, so return values need no explanation, and the critical preconditions and side effects are all present. What is missing is the already-enabled case and a pointer to how "no problems" is established, both of which matter for a destructive toggle.

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 coverage is 100% with a single parameter already documented as "the automation's id or name", so the description adds nothing beyond it. Baseline 3 applies when the schema carries all parameter meaning.

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 and resource ("Switch an automation on") and immediately defines the resulting state: it runs on every trigger event and its actions touch real licenses and customers. That is enough for an agent to separate it from disable_automation, test_automation and validate_automation without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions rather than implied ones: only on the user's request, only after a test run, only if the automation has no problems, and only if the caller holds the permissions the actions use. The reference to "after a test run" routes the agent to the test step first.

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