Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Copy Flow (Flow Designer)

copy_flow

Copy a ServiceNow Flow into your scoped application for safe modification. Returns the new sys_id and the now-sdk transform command to pull the flow locally.

Instructions

Copy an existing ServiceNow Flow Designer flow into a target scoped application. This is the best-practice first step when you want to modify any flow — OOB (out-of-box) and shared flows should not be modified directly. Copying into your application scope first keeps the original intact and gives you a flow you own and can freely modify.

This tool enables the full AI-assisted flow development lifecycle: copy_flow → pull with 'now-sdk transform' → modify → push → test_flow → publish_flow

The copied flow lands in draft/unpublished state in the target scope with a new sys_id, independent of the source. The tool returns the new flow's sys_id and prints the exact 'now-sdk transform' command to pull it locally.

Use list_scoped_apps to find the target_scope sys_id for your application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias to use. This is the alias configured via `now-sdk auth --add` (e.g., "myinstance", "prod", "test"). The user will typically refer to this by name when saying things like "on my myinstance instance". If not provided, falls back to the SN_AUTH_ALIAS environment variable.
source_flow_idYesSource flow sys_id (32-char hex) or scoped name (e.g., "global.change__standard"). This is the flow you want to copy. It can be an OOB flow, a flow in global scope, or a flow in any other application scope.
nameYesDisplay name for the newly created flow copy (e.g., "Copy of Change - Standard"). This becomes the flow's name in Flow Designer.
target_scopeYesScope sys_id of the target application to copy the flow into. This must be a sys_id (not a scope name). Use list_scoped_apps to find the sys_id for your application scope.
Behavior4/5

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

Discloses that the copied flow lands in draft/unpublished state with a new sys_id, independent of source. Also mentions it returns sys_id and a command. Lacks explicit permission info but no annotations to contradict.

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?

Well-structured with clear sections: action, rationale, lifecycle, behavior, tip. Each sentence adds value, though could be slightly more concise.

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?

Provides comprehensive context for a copy tool with no output schema: explains purpose, behavior, param details, and integration with other tools. Lacks error handling info but adequate.

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?

Schema coverage is 100%, but the description adds value beyond parameter descriptions: explains instance fallback, source_flow_id formats, and target_scope lookup via list_scoped_apps.

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 clearly states the verb 'Copy' and the resource 'ServiceNow Flow Designer flow'. It distinguishes from siblings by being the only copy tool, and explains it's the best practice first step for modifying flows.

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?

Explicitly states when to use: when modifying OOB or shared flows, and advises against direct modification. Provides a lifecycle pipeline and recommends using list_scoped_apps to find target scope.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sonisoft-cnanda/now-sdk-ext-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server