Skip to main content
Glama

sn_mcp_status

Read-only

Checks whether this instance's MCP servers are usable by verifying endpoint health, OAuth/JWT readiness, status, and tool counts, and returns fixes for issues.

Instructions

Check whether this instance's own MCP servers (ServiceNow MCP Server Console, Action Fabric) are usable from here: endpoint health, OAuth/JWT readiness of the current connection, and each server's status and tool count, with fixes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 only declare readOnlyHint and openWorldHint; the description adds real value by enumerating the three things verified (endpoint health, OAuth/JWT readiness of the current connection, per-server status and tool count). The trailing 'with fixes' is slightly ambiguous — it reads as remediations included in the report rather than mutations performed, but a careful agent gets no explicit confirmation that no changes are made.

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 that leads with the core question ('are usable from here') and then lists the checks. The parenthetical server names are informative rather than filler, though the colon-list-plus-trailing-phrase construction packs a lot into one sentence and slightly blurs 'with fixes'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only, no-output-schema diagnostic, the description covers what is checked, against which servers, and that remediation guidance comes back — everything an agent needs to decide to call it and interpret the answer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter hints are present.

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 names a specific verb ('Check') and a specific resource ('this instance's own MCP servers'), and enumerates what is inspected: endpoint health, OAuth/JWT readiness, per-server status and tool count. It is clearly distinguishable from siblings like sn_mcp_list_servers or sn_mcp_call_tool, though it never names those siblings explicitly.

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 implied by the phrase 'usable from here' — this is a diagnostic for troubleshooting connectivity/auth of the instance's own MCP servers. However, there is no explicit when-to-use/when-not-to-use statement and no routing to alternatives such as mcp_health_check or get_otto_status, so the agent must infer the selection criteria.

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