Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

manage_script_include

Manage ServiceNow script includes by listing, retrieving, creating, updating, deleting, or executing entries in sys_script_include, with filters for name, active status, and client-callable scripts.

Instructions

List/get/create/update/delete/execute a script include (table: sys_script_include).

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": {
      "action": "<action>"
    },
    "name": "manage_script_include"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoName search, or an encoded query
actionYes
activeNo
offsetNo
count_onlyNo
client_callableNoFilter by client_callable
script_include_idNosys_id or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.8
    • addedInput schema / properties / query / description
      Added value: +"Name search, or an encoded query"
  2. Changed2 schema fields changedv1.24.83
    • removedInput schema / properties / confirm
      Removed value: -{
      -  "enum": [
      -    "approve"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "confirm"
      -]New value: +[
      +  "action"
      +]
  3. Addedv1.21.21
  4. Removedv1.21.13
  5. First observedv1.18.41

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it fails: it advertises create/update/delete/execute (which would be mutating and destructive) while the schema only permits list/get, leaving the agent with a wrong model of the tool's blast radius. It says nothing about permissions, read-only nature, paging defaults, or what the response looks like.

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?

A single front-loaded sentence with zero padding, which is the right size for a tool with 8 mostly self-describing parameters. The brevity is only a problem because the content is inaccurate, not because it is bloated.

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 an 8-parameter tool with 38% schema coverage, no annotations, and no output schema, the description should at minimum explain the list-vs-get actions and the id/query filters. Instead the enumerated operations conflict with the actual enum, so an agent cannot rely on the description to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 38% across 8 parameters, so the description must compensate and does not. Only the resource/table is named; filtering semantics for active, client_callable, count_only, offset, limit, and the sys_id-or-name dual meaning of script_include_id are left entirely to the schema (and most have no schema text at all).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List/get/create/update/delete/execute a script include" names a resource and enumerates operations, and adds the backing table (sys_script_include), which is useful. But the operation list is boilerplate CRUD shorthand that does not match what the tool actually accepts (action enum is only list/get), and nothing distinguishes it from siblings like sn_query or search_server_code.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of generic query tools such as sn_query or sn_aggregate, nor on which action to pick for a given intent. The only implied usage is the action name itself.

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