Skip to main content
Glama

create_change_from_remediation_task

Creates a ServiceNow change from a Vulnerability Response remediation task, linking the task, vulnerable items, and affected CIs so task and change states stay in sync.

Instructions

Create a change for a Vulnerability Response remediation task (VUL...) the same way the "Create Change" action does (sn_vul.ChangeMgmt actionCreateChange): the change, its link to the task, the vulnerable item links and the affected CIs, so task and change states stay in sync. Requires WRITE_ENABLED=true and the server-side script runner

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": {
      "remediation_task": "<remediation_task>"
    },
    "name": "create_change_from_remediation_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
add_cisNoAdd the affected CIs to the change (default true)
end_dateNoPlanned end, YYYY-MM-DD HH:MM:SS
assigned_toNoAssignee sys_id (default: the task's)
change_typeNoChange type (default normal)
justificationNoJustification (recommended for emergency changes)
assignment_groupNoAssignment group sys_id (default: the task's)
remediation_taskYesVUL number or sys_id of the remediation task (sn_vul_vulnerability)
short_descriptionNoChange short description (default: the task's)
implementation_planNoImplementation plan (default: the task's preferred solution)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds real value beyond them: it discloses the cascade of objects created (change, task link, vulnerable item links, CIs) and the state-sync intent between task and change. It omits failure semantics — no warning about duplicates/re-invocation despite idempotentHint=false, and no partial-failure behavior.

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 purpose and the effect list are front-loaded, and the prerequisite clause is placed at the end where it is easy to check before calling. The middle clause is dense with a raw internal identifier (sn_vul.ChangeMgmt actionCreateChange) that adds length without much agent value, but overall it is a tight single sentence.

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 9-parameter mutation with no output schema, the essentials are covered: what is created, prerequisites, and the object to act on. However, since no output schema exists, the description should say what comes back (e.g., the new change's sys_id) and whether re-running duplicates work, given idempotentHint=false.

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%, including defaults for every optional parameter and an enum for change_type, so the schema already carries the parameter burden. The description only indirectly touches parameters by mentioning that CIs and item links get created/attached, which loosely maps to add_cis. Baseline 3 is appropriate.

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?

Names a specific verb and resource ('Create a change') and precisely scopes the source object ('for a Vulnerability Response remediation task (VUL...)'), plus it enumerates the side effects created (task link, vulnerable item links, affected CIs). It does not explicitly distinguish itself from the sibling create_change_request, so an agent must infer that routing from the VUL/VR scoping alone.

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

Usage Guidelines4/5

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

Gives clear context for use: a VR remediation task, mirroring the platform's 'Create Change' action, with prerequisites named ('Requires WRITE_ENABLED=true and the server-side script runner'). It stops short of any exclusion or alternative — nothing tells the agent when to prefer create_change_request or create_devops_change instead.

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