Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

workflow_runner

Execute a specific Splunk workflow by ID with adjustable parameters, time windows, and focus hosts. Supports core and contrib workflows for targeted troubleshooting.

Instructions

Execute any available workflow by ID with comprehensive parameter control and parallel execution.

This tool provides a flexible interface to execute both core (built-in) and contrib (user-contributed) workflows with full control over execution parameters and diagnostic context. It leverages the same parallel execution engine used by the dynamic troubleshoot agent for optimal performance.

Core Capabilities:

  • Universal Execution: Run any workflow by ID - core or contrib workflows

  • Parameter Flexibility: Full control over time ranges, focus areas, and complexity levels

  • Parallel Processing: Dependency-aware parallel task execution for optimal performance

  • Comprehensive Results: Detailed execution results with performance metrics and summaries

  • Progress Tracking: Real-time progress reporting during workflow execution

Key Parameters:

  • workflow_id (required): ID of workflow to execute (use list_workflows to discover)

  • problem_description (optional): Context about the specific issue being investigated

  • earliest_time/latest_time (optional): Time range for diagnostic searches (default: "-24h" to "now")

  • focus_index/focus_host/focus_sourcetype (optional): Specific focus areas for targeted analysis

  • complexity_level (optional): "basic", "moderate", "advanced" analysis depth (default: "moderate")

  • enable_summarization (optional): AI-powered result summarization (default: True)

Supported Workflows:

  • Core Workflows: missing_data_troubleshooting, performance_analysis

  • Contrib Workflows: Any custom workflows from contrib/workflows/ directory

Benefits:

  • Consistent interface for all workflow types

  • Optimized parallel execution with dependency management

  • Flexible parameter control for different scenarios

  • Comprehensive result analysis and reporting

  • Integration with existing workflow infrastructure

When to use

  • Use when you know the workflow ID to run (discover via list_workflows)

  • Use for executing core or contrib workflows with custom time windows and focus context

  • Use in automation pipelines that orchestrate troubleshooting by workflow ID

Arguments

  • See Key Parameters list above. All are optional except workflow_id.

Outputs

  • Detailed execution results, task results, summary, and metadata including execution timing

Perfect for executing specific workflows when you know exactly which diagnostic procedure you need to run, or for building automated troubleshooting pipelines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes
problem_descriptionNo
earliest_timeNo-24h
latest_timeNonow
focus_indexNo
focus_hostNo
focus_sourcetypeNo
complexity_levelNomoderate
enable_summarizationNo

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains parallel execution, progress tracking, and comprehensive results, but does not explicitly state if the tool is read-only or has side effects. However, it gives substantial behavioral context beyond just 'execute'.

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 long but well-structured with headers, bullet points, and sections like 'Core Capabilities', 'Key Parameters', and 'When to use'. It is front-loaded with the purpose, making it easy to scan. A slightly shorter version could improve conciseness.

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?

Given 9 parameters and no output schema, the description covers the tool's functionality, parameters, and use cases well. It mentions outputs like 'detailed execution results, task results, summary, and metadata', but lacks a precise return structure. Still, it provides enough context for effective use.

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 description coverage is 0%, but the 'Key Parameters' section provides detailed explanations for each parameter, including defaults and optional behavior. This adds significant value beyond the bare schema, making the tool easy to use.

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 'Execute any available workflow by ID' and outlines core capabilities. It distinguishes itself from sibling tools like 'workflow_builder' and 'workflow_requirements' by focusing on execution with comprehensive parameter control.

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

Usage Guidelines5/5

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

The 'When to use' section explicitly says 'Use when you know the workflow ID to run' and suggests discovering workflows via 'list_workflows'. It also mentions use in automation pipelines, providing clear guidance on when to use this tool vs alternatives.

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