Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

automation_catalog

Read-onlyIdempotent

Lists available automation triggers and actions, their data fields, settings, limits, and graph format; call it before drafting an automation or request one trigger's fields and example data.

Instructions

What automations can be built from: every trigger with its data fields (CEL variables and {{placeholders}}), every action with its settings, the limits, and how a graph is written. Call it before drafting an automation; with trigger, that trigger's fields with help and example data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "automation_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
triggerNoa trigger's key (e.g. validation.ip.new) or title: its fields with help and an example of its data. Leave out for the overview of every trigger and action

Output Schema

NameRequiredDescriptionDefault
limitsYes
actionsNo
triggersYes
graphFormatYes
commonFieldsYesfields every trigger has

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds context beyond that: the breadth of returned content (triggers, actions, limits, graph authoring) and the fact that the parameterized mode enriches results with help text and example data. It does not mention size or cost of the full overview, which is the one meaningful behavioral 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?

Two dense sentences with no filler; the content inventory is front-loaded and the call-to-action and parameter behavior follow. The telegraphic phrasing ('with trigger, that trigger's fields...') is slightly elliptical and would read more cleanly with a subject and verb.

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?

With one optional parameter, full schema coverage, a full annotation set, and an output schema to describe return shape, this description covers what an agent needs to decide to call it and how to choose between the two modes. Only the relative cost/scope of the unfiltered overview is left unstated.

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% and the schema description already states both forms ('a trigger's key ... or title' and 'leave out for the overview'), including an example key. The description restates the same two-mode behavior without adding format rules such as whether title matching is fuzzy or case-sensitive. Baseline 3 is correct given the schema does the heavy lifting.

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 enumerates exactly what the resource contains: every trigger with its data fields (CEL variables and {{placeholders}}), every action with its settings, the limits, and graph syntax. That clearly separates it from siblings like list_automations or create_automation, which operate on instances rather than the building-block catalog. It opens with a noun phrase rather than a verb, which makes it marginally less crisp than a 'Returns the catalog of...' formulation.

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?

'Call it before drafting an automation' gives an explicit ordering instruction tied to a concrete workflow, and the second clause explains the branching behavior of the trigger parameter. It stops short of naming when the tool is unnecessary (e.g., after a catalog snapshot is already in context), so it stops at 4 rather than 5.

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