Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

workflow_builder

Create, edit, and validate custom troubleshooting workflows for Splunk. Supports multiple modes for guided creation, template generation, and comprehensive validation including dependency analysis.

Instructions

Interactive tool for creating, editing, and validating custom workflows.

This tool provides comprehensive workflow development capabilities for creating custom troubleshooting workflows that integrate with the MCP Server for Splunk dynamic troubleshooting system. It supports multiple modes of operation to accommodate different workflow development needs.

Modes:

  • create: Interactive workflow creation with guided prompts

  • edit: Modify existing workflow definitions with validation

  • validate: Comprehensive validation of workflow structure and dependencies

  • template: Generate pre-built workflow templates for common use cases

  • process: Process and validate finished workflow definitions

Key Capabilities:

  • Step-by-step workflow creation with validation

  • Template generation for common workflow patterns

  • Comprehensive validation including dependency analysis

  • JSON output generation with proper formatting

  • Integration testing and compatibility verification

  • Processing of complete workflow definitions

Validation Features:

  • Schema compliance verification

  • Circular dependency detection

  • Tool availability checking

  • Context variable validation

  • Integration compatibility assessment

When to use

  • Use to create new workflows from templates or from scratch

  • Use to edit or validate an existing workflow JSON before contributing or running it

  • Use to generate templates and examples for standard categories (security, performance, data quality)

Arguments

  • mode (optional): "create", "edit", "validate", "template", or "process" (default: "create")

  • workflow_data (optional): JSON string or object when editing/validating/processing

  • template_type (optional): Template key when mode="template" (e.g., "minimal", "security")

  • file_path (optional): Path to workflow file when mode="validate"

Outputs

  • Structured results including validation summaries, templates, or processed workflow data

  • Ready-to-execute workflows that can be run with workflow_runner or the dynamic agent

Perfect for workflow contributors who need guided assistance in creating well-structured, validated workflows that integrate seamlessly with the dynamic troubleshoot agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNocreate
workflow_dataNo
template_typeNominimal
file_pathNo

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

No annotations provided, so full burden on description. It explains modes and capabilities but does not clearly state if the tool modifies state or is purely read-only/transformative. It mentions interactive creation but not side effects.

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?

Well-organized with sections, bullet points, and front-loaded purpose. Somewhat verbose but each section contributes value. Structurally sound for an AI agent to parse.

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?

Covers modes, capabilities, validation features, usage scenarios, arguments, and outputs. Lacks detailed output shape and prerequisites, but given the tool's complexity and absence of output schema, it is largely complete.

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

Parameters4/5

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

Schema has 0% description coverage. The description lists each parameter with context on when to use and what values are expected (e.g., mode values, template_type keys). Provides more meaning than the schema alone, though some enumerations are not exhaustive.

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 is for creating, editing, and validating workflows. It distinguishes from siblings like workflow_runner by focusing on development rather than execution.

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 'When to use' section provides clear guidance on creating, editing, validating, and generating templates. It does not explicitly exclude execution use cases, but the sibling name workflow_runner implies the alternative.

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