Itential MCP Server

Official

by itential

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Get Automations

get_automations

Read-onlyIdempotent

List automations startable through trigger_automation, covering workflows, agents, and compliance plans with enabled API endpoint triggers plus component types and route names.

Instructions

Get the automations that can be started via trigger_automation.

Returns a unified list of automations that have an enabled API endpoint trigger, regardless of component type (workflows, agents, compliance plans). Automations with no endpoint trigger, or only a disabled one, are not listed. Each entry includes the component_type discriminator and the route_name needed to trigger it via trigger_automation.

Use this when you need to see everything startable through trigger_automation. Use get_workflows when you only need workflow-type automations.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes	Response model for the unified automations collection. Wraps a list of AutomationElement objects covering all component types. Attributes: root: List of AutomationElement objects.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.14.1Oct 18, 2026

changedOutput schema / properties / result / items / description

Previous value: -"Represents a single automation from the Operations Manager. Automations are the\nexecution containers that wrap a component (workflow, agent, or compliance plan)\nand expose it for triggering. The component_type field discriminates between types.\n\nAttributes:\n    name: Human-readable name of the automation.\n    description: Description of the automation.\n    component_type: Type of the underlying component (workflows, agents, ucm_compliance_plan).\n    component_id: ID or UUID of the underlying component.\n    route_name: API route name for triggering this automation (use with trigger_automation);\n        None means no endpoint trigger has been created yet.\n    input_schema: JSON Schema describing the input the automation endpoint accepts.\n    last_executed: ISO 8601 timestamp of last endpoint trigger execution (null if never executed)."New value: +"Represents a single automation from the Operations Manager. Automations are the\nexecution containers that wrap a component (workflow, agent, or compliance plan)\nand expose it for triggering. The component_type field discriminates between types.\n\nAttributes:\n    name: Human-readable name of the automation.\n    description: Description of the automation.\n    component_type: Type of the underlying component (workflows, agents, ucm_compliance_plan).\n    component_id: ID or UUID of the underlying component.\n    route_name: API route name for triggering this automation (use with trigger_automation).\n    input_schema: JSON Schema describing the input the automation endpoint accepts.\n    last_executed: ISO 8601 timestamp of last endpoint trigger execution (null if never executed)."

changedOutput schema / properties / result / items / properties / route_name / description

Previous value: -"API route name for triggering this automation (use with trigger_automation);\nNone means no endpoint trigger has been created yet"New value: +"API route name for triggering this automation (use with trigger_automation)"

First observedv0.1.0Aug 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered structurally. The description adds real behavioral context: only automations with an enabled endpoint trigger appear, disabled or absent triggers are excluded, and each entry carries component_type and route_name. It does not mention pagination or ordering, but the output schema covers 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?

The core purpose and the trigger_automation linkage are front-loaded in the first two lines, then filtering rules and return fields, then routing guidance. It is slightly repetitive in restating 'trigger_automation' across three sentences, but every sentence carries information.

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 zero-parameter read tool with an output schema and full annotation coverage, the description supplies exactly what the structured fields cannot: the filter semantics (only enabled endpoint triggers), the component-type breadth, and the sibling routing rule. Nothing needed to call it correctly is missing.

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?

The tool takes zero parameters, so the schema has nothing to document and there is no parameter semantics to explain. The description appropriately spends no space on params, which is the correct treatment for a no-arg listing tool.

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 description states a specific verb and resource ('Get the automations') and immediately scopes it to those startable via trigger_automation, explicitly noting it spans component types (workflows, agents, compliance plans). It distinguishes itself from the sibling get_workflows without the agent needing to open either 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?

It gives an explicit when-to-use ('when you need to see everything startable through trigger_automation') and names the alternative (get_workflows) with the condition that selects it. It also pairs naturally with trigger_automation, making the read-then-trigger workflow obvious.

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

Deploy Server