Skip to main content
Glama
deslicer

MCP Server for Splunk

get_splunk_health

Check Splunk server connectivity and health status, including version and system information, for troubleshooting and validation purposes.

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
Behavior3/5

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

With no annotations provided, the description carries full burden. It adequately describes the tool's behavior: it performs a read operation (checking health), explains authentication requirements, and specifies the response format. However, it doesn't mention potential rate limits, error handling details, or whether the operation has side effects on the Splunk server.

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?

The description is well-structured with purpose statement, usage context, parameter details, and response format. Every sentence adds value, though the parameter explanations are quite detailed (appropriate given the schema coverage gap). It could be slightly more concise in the opening paragraph.

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 tool with 6 parameters, 0% schema coverage, no output schema, and no annotations, the description does an excellent job covering purpose, parameters, and response format. The main gap is lack of explicit error handling information, but overall it provides sufficient context for an agent to use the tool effectively.

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?

With 0% schema description coverage for 6 parameters, the description fully compensates by providing detailed semantic information for each parameter: purpose, examples, and default behavior. The 'Args' section clearly explains what each parameter does, including the important note about using server-configured connections when parameters aren't provided.

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's purpose with specific verbs ('Check', 'return') and resources ('Splunk server connectivity', 'comprehensive health status information'). It distinguishes itself from sibling tools by focusing on server health/connectivity rather than configuration, searches, or data retrieval like 'list_indexes' or 'run_splunk_search'.

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?

The description provides clear context for when to use the tool ('Essential for connectivity troubleshooting and server validation') and explains parameter behavior ('If connection parameters are not provided, uses the server's configured connection'). However, it doesn't explicitly state when NOT to use it or name specific alternative tools for related purposes.

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