servicenow-api

Check ci lifecycle not allowed ops transition

servicenow_check_ci_lifecycle_not_allowed_ops_transition

Read-onlyIdempotent

Checks if a CI lifecycle transition is allowed. Prevents invalid operational state changes in ServiceNow.

Instructions

Determines whether an operational state transition is allowed.

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": "servicenow_check_ci_lifecycle_not_allowed_ops_transition"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No
`params_json`	No		{}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Oct 19, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond the bare purpose – no statement of what inputs are needed, what the result means, or how the underlying openWorld lookup behaves.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally clean, but the sparseness is under-specification rather than effective conciseness given the tool's opaque parameters.

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 a check tool with no output schema and two undocumented pass-through parameters, the definition should explain required inputs and the meaning of an allow/disallow result. Neither is present, so an agent lacks enough to invoke or interpret it 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 0% for two opaque parameters ('params' and 'params_json'), and the description provides no information about what either should contain. With low coverage the description is expected to compensate, and it does not, leaving the agent unable to construct a valid call.

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?

The description gives a verb and resource ('Determines whether an operational state transition is allowed'), so the purpose is discernible but generic. It does not differentiate this tool from close siblings like servicenow_check_ci_lifecycle_not_allowed_action or servicenow_check_ci_lifecycle_compat_actions, and it omits the 'not allowed ops' qualifier present in the name/title.

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 when-to-use guidance, no prerequisites (e.g., a CI id or lifecycle context required), and no mention of the sibling check tools that answer related lifecycle questions. The agent must guess when this check applies versus the other check_ci_lifecycle_* tools.

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

Deploy Server