Skip to main content
Glama

sn_mcp_list_servers

Read-only

Lists ServiceNow MCP servers on an instance, including status, endpoint URL, and attached tools; filter by active, draft, or inactive status to inspect server registries.

Instructions

List the ServiceNow MCP servers defined on the instance (MCP Server Console registry, including out-of-box ITSM, ITOM, CMDB and SPM servers when installed), with status, endpoint URL and attached tools.

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

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.5/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 safety is covered. The description adds useful scope context (the registry includes out-of-box servers when installed) and discloses the return fields, but says nothing about pagination, result limits, or how external/unregistered servers are treated.

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?

A single front-loaded sentence with no filler; the parenthetical about out-of-box servers is informative rather than decorative. It is dense but every clause contributes scope 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 read-only listing tool with one optional enum parameter and no output schema, the description covers what is listed, where it comes from, and which fields come back. It stops short only on result-set size and relation to the near-identical registry sibling.

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 the single status parameter has an enum and inline description, so the schema carries the meaning. The description never references the status filter, so it adds nothing beyond the schema on this dimension.

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?

Names a specific verb and resource ("List the ServiceNow MCP servers defined on the instance") and clarifies the backing source is the MCP Server Console registry, including out-of-box ITSM/ITOM/CMDB/SPM entries. It does not distinguish itself from close siblings such as sn_mcp_list_registry or sn_mcp_list_tools, so an agent cannot fully disambiguate without opening schemas.

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 verb 'list' and the qualifier 'defined on the instance'; there is no explicit when-to-use statement, no exclusion of alternatives like sn_mcp_list_registry, and no note on when the status filter is appropriate.

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