Skip to main content
Glama
Sign In
servicenow-mcp-ai

servicenow-mcp-ai

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Switch connection profile

servicenow_use_instance
Idempotent

Switch the active ServiceNow connection profile for the current session, or persist it to the environment file when needed.

Instructions

Switch the connection profile (over HTTP: this session only unless persist).

Input Schema

NameRequiredDescriptionDefault
nameYesProfile to activate, e.g. 'dev'.
persistNoWrite the env file (journaled; default false).
instanceNoProfile (default active)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / instance / description
      Previous value: -"Connection profile to use for this call (default: the active profile). See servicenow_list_instances."New value: +"Profile (default active)"
    • addedInput schema / properties / instance / maxLength
      Added value: +128
    • changedInput schema / properties / name / description
      Previous value: -"Profile to activate, e.g. 'default' or 'dev'."New value: +"Profile to activate, e.g. 'dev'."
    • addedInput schema / properties / name / maxLength
      Added value: +128
    • addedInput schema / properties / persist
      Added value: +{
+  "description": "Write the env file (journaled; default false).",
+  "type": "boolean"
+}
  2. First observedv2.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark the tool as idempotent and non-destructive, and the description adds the important behavioral detail that over HTTP the switch is session-only unless persist is set. This clarifies the side effect of persist without contradicting the annotations. It does not state authentication requirements, but the annotations and schema cover the core safety profile.

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

Conciseness5/5

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

The description is a single tightly scoped sentence with the core action front-loaded and the session-persistence nuance in a parenthetical. Every part of it contributes 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 simple switch tool with no output schema and fully described parameters, the description covers the key behavioral nuance of session-only versus persist. It leaves out minor details such as what happens with an invalid profile name, but is otherwise sufficient for correct invocation.

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 the schema already documents name, persist, and instance. The description reinforces that persist controls session-only versus persisted switching, but adds little beyond the schema's own explanation of persist as writing the env file.

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?

The description uses a specific verb and resource: 'Switch the connection profile.' It is clearly distinguishable from sibling tools like servicenow_set_credentials and servicenow_list_instances, though it does not explicitly name an alternative.

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?

The description implies when to use the tool by saying it switches the active connection profile. It does not explicitly state when to prefer this over alternatives such as servicenow_list_instances or servicenow_test_connection, nor does it list any exclusions.

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