Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

update_automation

Destructive

Modify an automation's name, description, or full graph while keeping existing nodes in place and checking that enabled automations remain valid before the next run.

Instructions

Change an automation's name, description or whole graph. Nodes that keep their id keep their place on the canvas. An automation that is switched on must stay free of problems, and the change applies to its next run: confirm with the user first. A graph is {"nodes":[…],"edges":[…]}, a tree from exactly one trigger. Nodes: {"id","kind","type","config"}; kind is "trigger" (type: a trigger key, id "trigger"), "action" (type: an action key) or "condition" (no type; config {"cel": "<CEL expression over the trigger's fields>"}). Edges: {"from","to"} in the order nodes run; edges leaving a condition carry "branch": "true" (Yes) or "false" (No). Settings marked placeholders accept {{field.key}} from the trigger's fields, e.g. "{{license.id}}". CEL is typed: compare ints with ints (license.machinesUsed > 2), doubles with doubles (2.0), timestamps with timestamp("2026-01-01T00:00:00Z") or now ± duration("72h"); string fields with options only take those values.

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

Input Schema

NameRequiredDescriptionDefault
nameNoa new name
graphNothe whole new graph (get_automation shows the current one); left out keeps it
automationYesthe automation's id or name
descriptionNoa new description; empty string clears it

Output Schema

NameRequiredDescriptionDefault
nextYeswhat to do next
automationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds context annotations cannot express: the edit is deferred to the next run, an enabled automation must remain valid, the user should confirm first, and node ids determine canvas placement (implying unchanged ids survive, missing ones do not). That is substantive behavioural disclosure rather than a restatement of the hints.

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?

Purpose and the confirm-first rule are front-loaded, then the reference detail follows in a compact sequence. It is long and dense, but nearly every clause carries spec an agent needs to build nodes, edges, and conditions; only the graph shape restatement overlaps the schema.

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 destructive, non-idempotent mutation with an output schema already declaring return values, the description covers the graph format, node/edge semantics, condition expressions, placeholder substitution, CEL type constraints, and the confirmation requirement. Nothing essential to invoking it correctly is missing, though it could mention validation-failure behaviour.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds material the schema does not: the {{field.key}} placeholder syntax drawn from trigger fields and the CEL typing rules (int/int, double/double, timestamp()/now ± duration(), string fields restricted to option values). Those details are what actually let an agent construct a valid graph argument.

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?

The first sentence names a specific verb and resource and bounds the scope: name, description, or whole graph of an existing automation. It implicitly separates itself from create_automation and enable/disable_automation by framing the work as changing an existing definition, and it points at get_automation for viewing the current graph.

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 a real precondition (an enabled automation must stay problem-free) and an explicit behavioural rule: confirm with the user before applying, because the change only takes effect on the next run. It stops short of naming validate_automation or test_automation as the safer path when composing a new graph.

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