Skip to main content
Glama
deslicer

MCP Server for Splunk

get_splunk_health

Check Splunk server connectivity and retrieve comprehensive health status including version and system information. Supports custom connection parameters for testing different instances.

Instructions

Check Splunk server connectivity and return comprehensive health status information including server version, connection status, and system information. Supports both server-configured connections and custom connection parameters for testing different Splunk instances. Essential for connectivity troubleshooting and server validation.\n\nArgs:\n splunk_host (str, optional): Splunk server hostname or IP address (e.g., 'localhost', 'splunk.example.com', '10.1.1.100')\n splunk_port (int, optional): Splunk management port, typically 8089 (e.g., 8089, 8000, 9997)\n splunk_username (str, optional): Splunk username for authentication (e.g., 'admin', 'splunk', 'analyst')\n splunk_password (str, optional): Splunk password for authentication\n splunk_scheme (str, optional): Connection scheme - 'http' or 'https'\n splunk_verify_ssl (bool, optional): Whether to verify SSL certificates\n\nNote: If connection parameters are not provided, uses the server's configured connection.\n\nResponse Format:\nReturns dictionary with 'status', 'version', 'server_name', and 'connection_source' fields. Status can be 'connected' or 'error'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
splunk_hostNo
splunk_portNo
splunk_usernameNo
splunk_passwordNo
splunk_schemeNo
splunk_verify_sslNo
Behavior4/5

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

Describes the return format and possible statuses ('connected' or 'error'), indicating it is a read-only operation. No annotations are provided, so the description carries full burden. It doesn't explicitly declare read-only, but the nature of 'check connectivity' implies safety. Could be slightly more explicit, but satisfactory.

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?

The description is well-structured: purpose first, then connection mode note, then parameter list with examples, then default behavior, then response format. Every sentence adds value. No fluff. Front-loaded with the core action.

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?

Given 6 optional parameters, no annotations, and no output schema, the description covers all necessary information: tool purpose, parameter details, default behavior, and response format. An AI agent has everything needed to use the tool correctly.

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

Parameters5/5

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

Schema has 0% description coverage, so the description fully compensates by detailing each parameter's purpose, format, and example values (e.g., splunk_host: 'localhost', 'splunk.example.com'). Also explains default behavior when parameters are omitted. Adds significant meaning beyond the schema types.

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?

The description clearly states the tool checks Splunk connectivity and returns comprehensive health status including version and connection info. It uses specific verbs and resource, differentiating it from sibling tools by being the dedicated health check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to provide custom connection parameters versus using the default server configuration. Does not exclude any scenarios, but doesn't explicitly state when not to use the tool. The context is clear enough for an AI agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deslicer/mcp-for-splunk'

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