Schema | netdiag-mcp

netdiag-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
list_sitesA	List every site known to this diagnostics server.
site_healthA	Get the layered health status (circuit, power, core, access) for a site. site must exactly match a name returned by list_sites.
degraded_sitesA	List every site with at least one layer not reporting fully healthy.
root_causeA	Trace the most likely root-cause layer for a site's issues. Walks circuit, power, core, and access in dependency order and reports the first layer that isn't healthy, since an upstream issue typically explains downstream symptoms rather than being a separate problem. site must exactly match a name returned by list_sites.
redundancy_gapsA	List every (site, layer) pair currently lacking redundancy. Flags layers that aren't redundant even if their current status is healthy, since a non-redundant healthy layer is one failure away from an outage.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miservicespro/netdiag-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server