Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer

Run Oneshot Search

run_oneshot_search

Run a Splunk search and retrieve immediate results for quick lookups, ad-hoc checks, or previews. Returns up to 10,000 events with execution timing and the query used.

Instructions

Run a Splunk search and return results immediately (no job created). Use this when you need a quick lookup or small result set (typically under ~30s) such as simple stats, ad‑hoc checks, or previews. Do not use for long‑running or heavy searches—prefer run_splunk_search in those cases.

Outputs: returns up to 'max_results' events or rows with timing and the executed query. Security: results are constrained by the authenticated user's permissions.Args: query (str): The Splunk search query (SPL) to execute. Can be any valid SPL command or pipeline. The 'search' command is automatically prepended if needed. Examples: 'index=main error', '| metadata type=hosts', '| stats count by sourcetype' earliest_time (str, optional): Search start time in Splunk time format. Examples: '-15m', '-1h', '-1d@d', '2023-01-01T00:00:00' Default: '-15m' latest_time (str, optional): Search end time in Splunk time format. Examples: 'now', '-1h', '2023-01-01T23:59:59' Default: 'now' max_results (int, optional): Maximum number of results to return. Higher values may cause longer execution times. Range: 1-10000. Default: 100

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
latest_timeNonow
max_resultsNo
earliest_timeNo-15m
Install Server

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It covers key aspects: immediate return, no job creation, maximum result limit, timing and executed query in output, permission constraints, and automatic prepending of the 'search' command. It lacks explicit details on failure handling or rate limits, but the disclosed behaviors are comprehensive for a read tool.

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 well-structured with distinct sections for usage, outputs, security, and parameters. It is slightly verbose due to the parameter examples, but every sentence carries useful information. The front-loading of purpose and usage aids quick comprehension.

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?

Given the absence of annotations and an output schema, the description is remarkably complete. It covers what the tool does, when to use it, semantics of parameters, what output to expect, security constraints, and the automatic 'search' prepending. It even contrasts with the sibling tool. No critical gaps remain.

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?

Although the input schema itself has no descriptions (0% coverage), the description's 'Args' section thoroughly documents all four parameters: query (by valid SPL and examples), earliest_time and latest_time (with format examples and defaults), and max_results (with range and impact). This fully compensates for the schema gap.

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's purpose: it runs a Splunk search and returns results immediately without creating a job. It explicitly contrasts itself with run_splunk_search, distinguishing the oneshot nature and immediate execution. This is a specific verb+resource with clear scope.

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 description provides explicit guidance on when to use this tool (quick lookups, small result sets, ad-hoc checks) and when not to use it (long-running or heavy searches), and even names the preferred alternative (run_splunk_search). This leaves no ambiguity for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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