Skip to main content
Glama

create_agentic_workflow

Build an agentic workflow with ordered steps, conditions, and trigger rules, then link it to a parent AI agent for copilot or autopilot execution in ServiceNow.

Instructions

Create an agentic workflow linked to an AI agent (requires NOW_ASSIST_ENABLED + WRITE_ENABLED)

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": {
      "name": "<name>",
      "description": "<description>",
      "agent_sys_id": "<agent_sys_id>",
      "steps": "<steps>"
    },
    "name": "create_agentic_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWorkflow name
stepsYesOrdered list of workflow steps
descriptionYesWorkflow description
agent_sys_idYesSystem ID of the parent AI agent
execution_modeNocopilot (default) or autopilot
trigger_conditionsNoOptional trigger condition expression

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / execution_mode
      Added value: +{
      +  "description": "copilot (default) or autopilot",
      +  "type": "string"
      +}
  2. Addedv4.9.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the plugin/entitlement prerequisites, which is real value beyond annotations, but says nothing about side effects, whether a duplicate workflow is created on retry (non-idempotent), or what is returned.

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?

A single front-loaded sentence with the core action first and prerequisites in parentheses; nothing is wasted. It is arguably too terse for a six-parameter nested create operation, but every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with a nested ordered steps array and optional trigger/condition fields, the definition covers the basics but omits what happens on success (no output schema, so the returned workflow identifier should be mentioned) and gives no guidance on step sequencing or valid action values. Adequate but with clear gaps.

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 description coverage is 100%, so all six parameters including the nested step object fields are documented structurally. The description adds no meaning beyond the schema — no note about step ordering semantics, valid action identifiers, or how execution_mode interacts with the agent.

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?

States a specific verb and resource ('Create an agentic workflow') plus a key relational constraint ('linked to an AI agent'), which separates it from siblings like create_ai_agent or create_flow. It does not explicitly name which sibling to use instead, so it falls short of a 5.

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

Usage Guidelines3/5

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

The parenthetical '(requires NOW_ASSIST_ENABLED + WRITE_ENABLED)' gives a precondition for use, which is useful routing context. However, there is no guidance on when to choose this over create_flow or create_ai_agent, and no exclusions or alternative-selection criteria.

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

Deploy Server

Other Tools