Schema | NetPulse

NetPulse

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

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

Functions exposed to the LLM to take actions

Name	Description
ping_deviceA	Ping a network device and return round-trip time statistics. Args: target: IP address or hostname to ping. count: Number of ping packets to send (1-20, default 5).
run_tracerouteA	Run a simulated traceroute to a network device. Args: target: IP address or hostname of the destination. max_hops: Maximum number of hops (1-64, default 30).
check_interfaceB	Get detailed diagnostic information for a specific interface. Args: device: Hostname of the network device. interface: Interface name (e.g., GigabitEthernet0/0).
get_device_configA	Retrieve the running configuration of a network device (read-only). Args: device: Hostname of the network device. section: Config section (e.g., 'bgp', 'ospf'). Returns full config if empty.
compare_baselineA	Compare a device's current metric value against its rolling baseline. Args: device: Hostname of the network device. metric: Metric name (cpu_percent, memory_percent). window: Baseline window (for display context, default '24h').
restart_interfaceA	Restart (bounce) a network interface. REQUIRES explicit confirmation. This is a state-modifying action. You MUST set confirm=true to execute. If confirm is false or missing, an impact analysis is returned instead. Args: device: Hostname of the network device. interface: Interface name to restart (e.g., GigabitEthernet0/0). confirm: Must be explicitly set to true to execute the restart.

Interactive templates invoked by user choice

Name	Description
`network_health_summary`	Generate a comprehensive network health briefing. Reads all available resources and produces a structured NOC briefing with overall health score, devices requiring attention, bandwidth utilization trends, active incidents, and recommended actions.
`troubleshoot_connectivity`	Diagnose connectivity issues between two network endpoints. Args: source: Source device hostname or IP. destination: Destination device hostname or IP.
`capacity_planning`	Analyze bandwidth utilization and project capacity needs. Reads bandwidth and interface data to identify links approaching capacity limits and recommend upgrade timelines.

Contextual data attached and managed by the client

Name	Description
`device_status`	Returns status of all monitored network devices with summary counts.
`latency_report`	Returns ping latency matrix between all monitored endpoints with threshold context.
`bandwidth_top_talkers`	Returns top 10 bandwidth consumers by source/destination.
`topology_map`	Returns network topology as nodes and edges with health status per link.
`active_alerts`	Returns all currently firing alerts with severity, source, and duration.

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hind77/Netpulse'

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