Skip to main content
Glama
deslicer

MCP Server for Splunk

create_dashboard

Creates a Splunk dashboard from Studio JSON or Classic XML. Supports overwriting existing dashboards and setting access permissions.

Instructions

Create a new dashboard in Splunk. Accepts Classic Simple XML (string) or Dashboard Studio JSON (object/string) via eai:data. Optionally overwrite if it exists and set sharing/permissions (ACL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDashboard name (required)
definitionYesStudio JSON (dict/string) or Classic XML (string) (required)
ownerNoDashboard owner. Default: 'nobody'nobody
appNoApp context. Default: 'search'search
labelNoHuman label shown in UI
descriptionNoDashboard description
dashboard_typeNo'studio'|'classic'|'auto' (default: 'auto')auto
sharingNo'user'|'app'|'global'
read_permsNoRoles/users granted read
write_permsNoRoles/users granted write
overwriteNoIf True, updates existing dashboard of same name
themeNoDashboard Studio UI theme when the tool wraps JSON into XML: 'light' or 'dark' (default: 'light'). Ignored for Classic Simple XML and when you pass a pre-wrapped Studio XML string (already containing <dashboard>).light
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: creation, acceptance of two formats, optional overwrite, and ACL settings. It adequately informs the agent of 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.

Conciseness5/5

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

Two sentences that are front-loaded with the action and no unnecessary words. Every sentence adds essential information.

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 12 parameters and no output schema, the description covers creation, formats, overwrite, and permissions. It lacks return value hints but is sufficient for a create action.

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?

The description adds value beyond the 100% schema coverage by explaining 'eai:data' and summarizing ACL capabilities, providing a clearer mental model for parameter usage.

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 'Create a new dashboard in Splunk' with specific resource and verb, and distinguishes from sibling tools like list_dashboards and get_dashboard_definition.

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 creating a dashboard, including formats, overwrite, and ACL options. It lacks explicit alternatives but the use case is evident.

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