Skip to main content
Glama
jshsakura

mfa-servicenow-mcp

by jshsakura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

manage_flow_designer

Inspect and analyze ServiceNow Flow Designer structures, conditions, executions, and action sources. Compare flows across instances to identify issues without editing.

Instructions

Flow Designer read/analyse: structure, conditions, executions, cross-instance compare, action source. Read-only - edit flows in the Flow Designer UI. (confirm='approve')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
scopeNoScope namespace
actionYesRead-only: list/get_detail/get_executions/compare/get_action_source/read_action. Edit flows in the Flow Designer UI.
offsetNo
confirmYes
flow_idNoFlow sys_id; get_detail also accepts flow_name instead
node_idNoAction/logic/trigger instance id; on get_detail reads that ONE step in full
flow_nameNoFlow name: get_detail exact/contains lookup, or executions filter
flow_typeNoflow (default) | subflow | all | action | playbook | decision
action_refNoAction sys_id/name; discover via action=list with flow_type=action
context_idNoExecution sys_id (sys_flow_context)
count_onlyNo
exec_stateNoComplete/Error/Waiting/Cancelled/In Progress
trace_pillNoTrace data pill through flow
errors_onlyNo
flow_statusNoStatus: Draft/Published/etc
name_filterNoName contains-match
source_recordNoSource record display value
summary_formatNoCompact format; False = raw JSON
confirm_publishNo
include_inactiveNo
include_triggersNo
include_versionsNo
include_structureNo
include_subflow_treeNo
include_executions_summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.24.67
    • changedInput schema / properties / action / description
      Previous value: -"Writes (checkout/set_*/add_branch/save/publish/activate/deactivate/copy/update) need browser auth; rest are reads."New value: +"Read-only: list/get_detail/get_executions/compare/get_action_source/read_action. Edit flows in the Flow Designer UI."
  2. Changed1 schema field changedv1.24.61
    • addedInput schema / properties / node_id
      Added value: +{
+  "description": "Action/logic/trigger instance id; on get_detail reads that ONE step in full",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.23.8
    • addedInput schema / properties / confirm_publish
      Added value: +{
+  "enum": [
+    "approve"
+  ],
+  "type": "string"
+}
  4. Addedv1.21.20
  5. Removedv1.21.13
  6. First observedv1.18.41

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It explicitly labels the tool read-only and points editing to the UI, and it notably promotes 'confirm='approve'', though much of this duplicates the schema's own 'Read-only' text. It does not disclose output format, pagination, or quirks like how counts and raw JSON work.

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 description is compact and mostly front-loaded with the core read/analyse purpose, followed by the read-only caveat and confirm requirement. The final clause is slightly cryptic but the overall text is efficient.

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

Completeness2/5

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

For a 27-parameter, no-output-schema tool with no annotations, this description is too sparse. It mentions 'cross-instance compare' and 'read_action' in the action param description, yet the action enum lacks compare/read_action values, so an agent cannot reliably map the advertised features to valid invocations.

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 52% and many parameters lack descriptions, but the description names the high-level capability clusters (conditions, executions, action source, compare) that map to several parameters. It does not compensate for undocumented params such as offset, limit, count_only, or include_triggers or explain how confirm differs from confirm_publish.

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 names a specific resource (Flow Designer) and a clear purpose: read/analyse structure, conditions, executions, cross-instance compare, and action source. It is not a tautology and gives more specificity than the tool name alone, though it does not explicitly differentiate itself from sibling tools like manage_workflow.

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 phrase 'Read-only - edit flows in the Flow Designer UI' gives a clear context: use this tool for read/analysis and go to the UI for edits. It does not, however, address when to choose this tool over siblings or state any other exclusions.

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