Skip to main content
Glama

sn_mcp_list_registry

Read-only

Lists external MCP servers registered on a ServiceNow instance, showing endpoint URLs, authentication, AI agent tools built on each, and whether MCP tools are enabled.

Instructions

List the EXTERNAL MCP servers registered on the instance's MCP client (sn_mcp_server, used by AI Agent Studio to give ServiceNow AI agents tools from outside MCP servers), with endpoint URL, auth, the AI agent tools built on each, and whether MCP tools are enabled for AI agents (sn_aia.enable_mcp_tool).

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_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFilter by name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond them: it names the returned fields (endpoint URL, auth, derived AI agent tools) and explains that the MCP-tools-enabled flag is governed by the sn_aia.enable_mcp_tool property, which an agent needs in order to interpret results; only pagination/result limits are undisclosed.

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?

It is a single front-loaded sentence that leads with the action and resource before the explanatory parentheticals, so nothing is buried. The nested parentheses around sn_mcp_server and sn_aia.enable_mcp_tool make it slightly run-on, but every clause carries 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 read-only list tool with one optional parameter and no output schema, the definition enumerates the returned field categories, which compensates for the absent output schema. Missing only pagination/volume expectations, which are minor at this complexity.

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?

The single optional 'search' parameter has 100% schema description coverage ('Filter by name'), and the description never mentions it. With the schema doing all the work, the baseline of 3 applies; no filter syntax or matching behavior is added.

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?

Specific verb ('List') plus a precisely scoped resource ('EXTERNAL MCP servers registered on the instance's MCP client'), with the backing table named (sn_mcp_server). The capitalized EXTERNAL plus the Agent Studio context clearly separates it from the sibling sn_mcp_list_servers without the agent needing to open either schema.

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 use case (inventorying externally registered MCP servers and their AI agent tools) is implied by the scope, but there is no explicit when-to-use or when-not-to-use statement and no routing to alternatives such as sn_mcp_register_external_server or sn_mcp_unregister_external_server for mutation. Guidance is inferable rather than stated.

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