Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

get_automation

Read-onlyIdempotent

Retrieve an automation's graph, nodes, edges, and problems to explain it or prepare changes with update_automation.

Instructions

One automation with its graph (nodes and edges) and problems, to explain it or to change it with update_automation.

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

Input Schema

NameRequiredDescriptionDefault
automationYesthe automation's id or name

Output Schema

NameRequiredDescriptionDefault
idYes
linkYesthe automation in the dashboard's editor
nameYes
graphYesnodes and edges (the editor's positions left out)
enabledYesswitched on: it runs on every trigger event
triggerNothe trigger's key
versionYes
problemsNowhat keeps it from being tested or switched on; none = ready
updatedAtYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds useful framing (it returns graph structure plus 'problems', and pairs with update_automation) but nothing about failure behavior when the id/name doesn't resolve, since the output schema already documents the return shape.

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 compact sentence with the resource and its payload front-loaded and the sibling reference at the end. It is telegraphic to the point of slight awkwardness ('and problems'), but nothing is wasted.

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?

With a one-parameter schema at full coverage, rich annotations, and an output schema documenting the return, the description needs only to convey purpose and the read-before-update workflow, and it does both. Nothing an agent needs to invoke it correctly is missing.

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?

There is a single parameter with 100% schema description coverage ('the automation's id or name'), so the schema fully documents it. The description adds no lookup-resolution detail such as whether name matching is exact or case-sensitive, leaving the baseline of 3 appropriate.

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?

The description states a specific resource and scope: one automation (not a list) returned with its graph (nodes and edges) and problems. That distinguishes it from list_automations and from mutation siblings, though the retrieval verb itself is only implied rather than stated.

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?

It gives a concrete usage context: fetch this to explain an automation, or as the read step before changing it via update_automation. That effectively names the alternative and the workflow, but there are no explicit exclusions or preconditions beyond that.

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