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 with guided prompts, templates, and 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

A3.5/5.0
Behavior2/5

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

No annotations are provided; the description mentions validation, creation, and editing but does not disclose whether operations are persistent, require authentication, or have side effects (e.g., overwriting existing data). It says 'processing of complete workflow definitions' but lacks details on outcomes. Significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long with multiple sections, some redundancy (e.g., modes repeated). Structure with headings and bullet points helps readability, but could be more concise by merging overlapping content like 'Key Capabilities' and 'Validation Features'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given complexity (4 params, no annotations, no output schema), description covers purpose, modes, usage guidance, arguments, and outputs. However, lacks behavioral transparency (see dimension 3) and could detail parameter constraints more. Adequate but not fully comprehensive.

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

Parameters3/5

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

Schema coverage is 0%, so description must compensate. The 'Arguments' section explains mode, workflow_data, template_type, and file_path with usage context and defaults. However, details like allowed values for mode are listed in the description but not enforced in schema, and format of workflow_data is not specified. Adds some meaning but 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 custom workflows,' with specific modes (create, edit, validate, template, process). It distinguishes from siblings like workflow_runner (which runs workflows) and workflow_requirements, making the purpose unambiguous.

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 explicitly mentions creating, editing, and validating workflows, and generating templates. It implies not to use for running workflows (workflow_runner), but does not explicitly name alternatives. Clear context, minor omission.

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