now-sdk-ext-mcp

Clone Update Set

clone_update_set

Create a new update set by copying records from an existing one, keeping only basic capture fields; intended only when a simple clone is explicitly requested.

Instructions

Clone an existing update set by creating a new one and copying its records.

WARNING: do not use this to move or promote work. The copy keeps only a few columns of each capture (name, type, target_name, payload, category): it drops application (the copies default to global), action, table, replace_on_upgrade, update_guid and sys_recorded_at, so the clone does not commit like the original. To move a capture use move_update_set_capture; to ship a set, complete it and export_update_set. Use this only when the user asks for a clone knowing that.

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": {
      "source_sys_id": "<source_sys_id>",
      "new_name": "<new_name>"
    },
    "name": "clone_update_set"
  }
}

Input Schema

Name	Required	Description
`instance`	No	The ServiceNow instance auth alias to connect to. This is the alias configured via `snc configure` (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.
`new_name`	Yes	The name for the new cloned update set.
`source_sys_id`	Yes	The sys_id of the update set to clone.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.1May 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare the generic safety profile (not read-only, not destructive, not idempotent, open-world); the description goes far beyond by enumerating exactly which columns are dropped (application, action, table, replace_on_upgrade, update_guid, sys_recorded_at) and which survive. It also discloses the consequential side effect that copies default to the global scope and that the clone will not commit like the original.

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?

Structure is strong: the mechanism comes first, followed by a WARNING block that front-loads the risky misuses, then the alternatives, then the permitted condition. The dropped-column list is dense but each item carries real information; a small amount of repetition between the opening and closing sentences keeps it just short of a 5.

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?

For a mutation tool with no output schema, the description covers mechanism, data loss, scope side effects, and routing to alternatives. It does not say what the call returns (e.g., the new sys_id) or discuss permission/instance prerequisites, which leaves a minor gap given the 100%-covered schema.

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%, so instance, new_name, and source_sys_id are already documented in the input schema. The description adds no further syntax, format, or constraint detail about the parameters, so the baseline 3 applies.

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 opens with a specific verb and resource — 'Clone an existing update set by creating a new one and copying its records' — which states both the operation and its mechanism. It is clearly differentiable from siblings like create_update_set, move_update_set_capture, and export_update_set, which are named explicitly.

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 states a hard exclusion ('do not use this to move or promote work'), names the correct alternative for each mistaken use case (move_update_set_capture for moving a capture, complete it + export_update_set for shipping a set), and gives the positive condition ('use this only when the user asks for a clone knowing that').

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

Deploy Server