Skip to main content
Glama

get_release_info

Read-only

Retrieve the ServiceNow release your instance runs, upcoming family, breaking changes with impact counts, and upgrade history to plan safe upgrades.

Instructions

Which ServiceNow release the instance runs (glide.buildtag.last: family, patch, hotfix), the next family, and the known breaking or behaviour changes on the way (Australia, Brazil), each with a live count of what on this instance it could affect and a list link. Also the recent upgrade history (sys_upgrade_history). Read-only

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

Input Schema

NameRequiredDescriptionDefault
include_checksNoCount what each known change could affect on this instance (default true)
target_releaseNoTarget family, e.g. "brazil". Default: the next family after the current one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the trailing 'Read-only' is redundant and earns nothing. The description does add genuine context beyond the annotations: it discloses the underlying data (glide.buildtag.last, sys_upgrade_history) and that per-change counts are computed live against this instance, but it never warns that those counts may be expensive or slow, which is the main behavioural risk here.

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?

The core purpose is front-loaded, which is good, but the body is a single dense run-on sentence packed with parenthetical asides (glide.buildtag.last, Australia/Brazil, sys_upgrade_history) that slows parsing. The closing 'Read-only' duplicates the annotations and is pure waste.

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 two-optional-parameter read tool with no output schema and full schema coverage, the description covers enough: what release data is returned, what the change list contains, what the counts mean, and that history is included. Only the cost/scale of the live counting is left unstated.

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%, so both parameters are already documented, including the include_checks default and the target_release default. The description reinforces the defaults ('the next family', live counts) and supplies example family values, but adds no new syntax or constraint beyond the schema – baseline 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?

The description names a specific resource and scope: the instance's ServiceNow release (family, patch, hotfix), the next family, the breaking/behaviour changes en route, and the recent sys_upgrade_history. Nothing in the sibling list plausibly overlaps with release/build metadata, so the tool is easy to disambiguate from names alone.

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 is only implied by the content (checking release level, upcoming family, known breaking changes, upgrade history) – typical pre-upgrade or impact-assessment context. There is no explicit 'use this when…' or 'use X instead for…' routing, though the narrow subject matter makes mis-selection unlikely.

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