Skip to main content
Glama

run_fix_script

Executes a ServiceNow fix script by name or sys_id, optionally asynchronously, to apply server-side fixes when write and scripting are enabled.

Instructions

Execute a fix script (sys_script_fix) by name or sys_id on the server. Requires WRITE_ENABLED=true and SCRIPTING_ENABLED=true

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_fix_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFix script name
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
sys_idNosys_id of the fix script

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. Addedv4.15.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description still adds real value by disclosing server-side configuration gates (WRITE_ENABLED=true, SCRIPTING_ENABLED=true) that will block execution. It omits failure semantics and any warning that this runs arbitrary server-side code.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding: action and addressing first, prerequisites second. Every clause carries information an agent needs before calling.

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 three-optional-parameter execution tool with no output schema, the definition covers what it acts on and the configuration preconditions that gate it. The remaining gap is behavioral: what a caller gets back on success versus failure and what happens if both name and sys_id are supplied, though the schema partially covers the job_id return path.

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% and the schema itself documents 'async' in detail, including get_job polling and the ~20 second auto-switch to a background job. The description only restates the name/sys_id addressing already in the schema, adding no extra meaning. Baseline 3 applies.

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: 'Execute a fix script (sys_script_fix)', plus the two addressing keys ('by name or sys_id'). The target table name removes ambiguity. It stops short of distinguishing itself from sibling 'execute_script' / 'execute_background_script', so an agent must infer the difference.

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?

Use is implied (run a fix script on the server) and the WRITE_ENABLED/SCRIPTING_ENABLED prerequisite functions as a use condition. However, there is no explicit when-to-use-vs-alternatives guidance, no note on choosing name vs sys_id, and no mention of when the async path should be preferred even though the sibling 'get_job' would be involved.

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