Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_check_plan

Read-only

Compare a saved plan with the current record to confirm it can still be applied, or report post-apply/undo drift and the last editor without making changes.

Instructions

Compare a saved plan with the record as it is now. Before the plan is applied it says whether it can still be applied, or whether the record changed since the plan was made. After it is applied or undone it reports drift: each planned field that no longer holds the value sn_apply_plan or sn_undo_plan left there, and who changed the record last. Only reads.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "sn_check_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe plan_id that sn_plan_change returned. Example: 20261016-101500-1a2b3c4d.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description reinforces this with 'Only reads' rather than contradicting it. It adds useful behavior beyond the annotations – per-field drift detection against values left by sn_apply_plan/sn_undo_plan, and last-modifier reporting – but says nothing about permissions, error cases, or whether comparison is scoped to specific fields.

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?

Three tight sentences, front-loaded with the core action and then split cleanly by before/after states. Minor wordiness in the first sentence ('or whether the record changed since the plan was made'), but every sentence contributes distinct 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 one-parameter read-only tool with no output schema, the description covers what matters: what is compared, the two result regimes, and the shape of drift reporting including last-editor attribution. Full completeness would require stating the response structure or what a clean (no-drift) result looks like.

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%, with plan_id documented and an example value supplied by sn_plan_change. The description adds no additional meaning about the parameter, so the baseline of 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?

States a specific verb and pair of resources ('Compare a saved plan with the record as it is now') and scopes it to two distinct modes: pre-application feasibility and post-apply/undo drift. An agent can distinguish this read-only comparison from sn_apply_plan, sn_undo_plan and sn_plan_change without opening any schema.

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 explicit call contexts: before applying, to verify the plan is still applicable or detect that the record changed; after apply/undo, to report drift. It does not spell out a when-not-to-use case or say 'use sn_apply_plan to actually apply', but the operational context is clear.

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