Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_workflows

Discover all available troubleshooting workflows in Splunk. List core and contrib workflows with optional category filter.

Instructions

List all available workflows from core and contrib sources.

This tool provides a comprehensive listing of troubleshooting workflows available in the MCP Server for Splunk system. It discovers and lists both built-in core workflows and user-contributed workflows from the contrib directory.

Output Formats:

  • detailed: Complete workflow information with descriptions and metadata (default)

  • summary: Brief overview with workflow IDs, names, and basic statistics

  • ids_only: Simple list of workflow IDs for programmatic use

  • by_category: Workflows organized by category (security, performance, etc.)

Workflow Sources:

  • Core Workflows: Built-in system workflows (missing_data_troubleshooting, performance_analysis)

  • Contrib Workflows: User-contributed workflows from contrib/workflows/ directory

Key Information Provided:

  • Workflow ID and human-readable name

  • Description and purpose of each workflow

  • Number of tasks and dependency information

  • Source (core vs contrib) and validation status

  • Category and organizational information

  • Integration instructions for dynamic troubleshoot agent

When to use

  • Use when you need to discover which workflows exist before running one

  • Use to filter by category or get just workflow IDs for programmatic selection

Arguments

  • format_type (optional): "detailed" (default), "summary", "ids_only", or "by_category"

  • include_core (optional): Include built-in workflows (default: true)

  • include_contrib (optional): Include contrib workflows (default: true)

  • category_filter (optional): Filter by category (e.g., "security", "performance")

Outputs

  • Workflow listings in the requested format, discovery metadata, and category summaries

  • Note: Only workflows available in this server are listed (core + any contrib present)

Perfect for discovering available troubleshooting capabilities and selecting the right workflow for specific Splunk problems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
format_typeNodetailed
include_coreNo
include_contribNo
category_filterNo

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explains output formats, workflow sources, and notes that only available workflows are listed. It does not mention read-only nature explicitly but implies non-destructive behavior. Could add permission needs or rate limits.

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-structured with clear sections (main, output formats, sources, when to use, arguments). Some redundancy (e.g., workflow sources repeated in key info) could be trimmed, but overall efficient and front-loaded.

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?

Comprehensive for a listing tool with no output schema. Explains return formats, key information provided, and limitations. Covers discovery use case thoroughly and addresses programmatic needs.

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?

Input schema has 0% description coverage, but the description's 'Arguments' section fully documents each parameter with detailed meaning, defaults, and effects (e.g., format_type enum values, include flags, category_filter). Adds significant value beyond the schema.

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 'List all available workflows from core and contrib sources', specifying the verb and resource. It distinguishes from sibling list_* tools (e.g., list_apps, list_dashboards) by focusing on workflows, and mentions integration with dynamic troubleshoot agent.

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 gives clear scenarios: discover workflows before running one, filter by category, or get IDs for programmatic use. It implies when to use but does not explicitly state when not to use or mention alternatives like workflow_runner.

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