Skip to main content
Glama

sn_mcp_list_tools

Read-only

Discovers and lists the tools exposed by a ServiceNow MCP server, including input schemas and annotations, via a live MCP request after OAuth sign-in.

Instructions

List the tools a ServiceNow MCP server exposes (live tools/list over MCP, with input schemas and annotations). Needs an OAuth (JWT) sign-in; see sn_mcp_status.

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

Input Schema

NameRequiredDescriptionDefault
serverYesServer name, e.g. sn_mcp_server_default

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value beyond that: the call performs a live MCP tools/list (not a cached/registry read), returns input schemas and annotations as payload, and requires JWT auth — all behavior an agent can't get from the annotations alone.

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?

Two sentences, no filler, with the core action and its return content front-loaded and the auth prerequisite trailing. Every clause carries distinct 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 one-parameter read-only listing tool with no output schema, the description covers action, source of truth (live MCP), returned fields, and auth requirement — enough to call it correctly. Only minor gaps remain, such as error behavior on an unreachable or unauthenticated server.

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 'server' parameter already documents itself with its example value. The description mentions the server only as context, adding no syntax, formatting, or defaulting detail beyond the schema, so the baseline 3 applies.

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 a specific verb and resource ('List the tools a ServiceNow MCP server exposes') and scopes it further with 'live tools/list over MCP, with input schemas and annotations.' The word 'live' implicitly separates it from registry-style siblings like sn_mcp_list_registry, but no sibling is named, so differentiation is inferred rather than explicit.

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?

Adds a real prerequisite ('Needs an OAuth (JWT) sign-in') and routes the agent to sn_mcp_status for that step, which is genuinely useful. However, it never says when to prefer this over sn_mcp_list_registry or how it relates to sn_mcp_call_tool, so usage context is only partially established.

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