Skip to main content
Glama

sn_mcp_activate_server

Activate or deactivate a ServiceNow MCP server and optionally attach tool definitions by name, enabling admins to configure MCP Server Console entries with required write access and admin role.

Instructions

Activate or deactivate a ServiceNow MCP server, and optionally attach tool definitions to it by name (admin setup helper for MCP Server Console). REQUIRES WRITE_ENABLED=true and the sn_mcp_server.admin role.

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": {
      "server": "<server>"
    },
    "name": "sn_mcp_activate_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesServer name or sys_id
statusNoNew status (default active)
add_toolsNoTool definition names to attach, e.g. ["sn_mcp_server.incident_summarization"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

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 the required environment flag and admin role, plus the default status of 'active' — concrete operational context for a mutation tool. It does not explain whether add_tools appends to or replaces the existing tool set, which is the main behavioral unknown for this call.

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?

A single front-loaded sentence covering both operations, followed by a compact prerequisite clause. No filler, no restatement of the tool name.

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 three-parameter mutation tool with annotations and no output schema, the definition covers purpose, prerequisites, and defaults adequately. The remaining gap is the append-vs-replace semantics of add_tools and whether deactivating affects attached tools.

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 coverage is 100% and every parameter carries its own description and enum, so the schema already does the heavy lifting. The description only echoes 'by name' for add_tools and the default status, adding no semantics beyond the structured fields.

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 specific verbs (activate/deactivate) and the resource (ServiceNow MCP server), plus a secondary capability (attach tool definitions by name). This clearly separates it from sn_mcp_create_server/sn_mcp_delete_server, though the overlap with sn_mcp_add_tool for the add_tools capability is never addressed.

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?

Labels itself an 'admin setup helper for MCP Server Console' and states the prerequisites (WRITE_ENABLED=true, sn_mcp_server.admin role), which frames when it is usable. It gives no guidance on when to use this versus sn_mcp_add_tool for attaching tools, or versus sn_mcp_status for reading state, so usage must be inferred.

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