Skip to main content
Glama
Sign In
now-sdk-ext-mcp

now-sdk-ext-mcp

by sonisoft-cnanda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set Choice

set_choice
DestructiveIdempotent

Add or change a table column's list choice in a ServiceNow app and update set, setting label, sequence, hint, or inactive status; choice capture is verified in that update set.

Instructions

Add a choice to a column's list, or change one (label, sequence, hint, inactive), in the list's application and the named update set; the list's capture is verified there. Inactivating keeps the label and hides it from new selections.

Input Schema

NameRequiredDescriptionDefault
hintNoHint shown for the choice.
labelNoThe label. Required to add a choice.
scopeNoThe record's application: its scope name (e.g. "x_acme_app"), or "global". Give this or scope_id.
tableYesThe table.
valueYesThe stored value; it identifies the choice in the list.
columnYesThe column, prefix included (u_ in Global).
inactiveNoInactivate (true) or reactivate (false).
instanceNoThe 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.
languageNoChoice language (sys_choice.language, e.g. en, pb); en when omitted.
scope_idNoThe record's application by sys_scope sys_id, instead of scope.
sequenceNoPosition in the list.
update_setYessys_id of an In progress update set of that application (create_update_set). The capture is verified there; for adding a column and for layout saves it must also be the working set (set_current_update_set).
acknowledge_upgrade_skipNoOnly for an installed Store application, and only after the user has reviewed the change: upgrades of that application then skip this file until the customization is reviewed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.5.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that the change lands in the list's application and the named update set, that the capture is verified there, and that inactivating retains the label while hiding it from new selections. This adds real operational context that readOnly/destructive/idempotent hints alone do not convey.

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?

Two sentences, front-loaded with the verb and action, with no filler. The second clause is dense and slightly run-on but every phrase carries information.

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 13-parameter mutation tool with no output schema, the description covers the core action, the update-set capture requirement, and the inactive semantics; remaining gaps (scope selection, error behavior) are documented in the fully covered schema.

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%, so baseline is 3, and the description adds extra meaning for the 'inactive' parameter (label retained, hidden from new selections) plus the update_set capture/verification constraint, pushing it above baseline.

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: "Add a choice to a column's list, or change one" and enumerates the editable facets (label, sequence, hint, inactive). It is clearly distinct from get_choice_list and remove_choice, though it never names them explicitly.

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?

Usage context is implied by the add-vs-change framing and the update_set capture requirement, but there is no explicit when-to-use guidance, no mention of reading with get_choice_list first, and no prerequisites or exclusions stated.

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