splunk-mcp-server

search_splunk

Run SPL queries against Splunk logs to retrieve events. Set time range and limit results for focused analysis.

Instructions

Search Splunk logs with the given query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_splunk"
  }
}

Input Schema

Name	Required	Default
`query`	Yes
`earliest_time`	No	-1h
`latest_time`	No	now
`max_count`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

C2.1/5.0

Behavior1/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. The description only states 'Search Splunk logs with the given query' and fails to mention any traits such as time range handling, default values, read-only nature, or performance considerations. This is insufficient for an agent to understand the tool's behavior.

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

Conciseness2/5

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

The description is concise (one sentence), but it is too brief and lacks structure that would add value. While front-loaded with the action, it does not earn its place by providing any additional information beyond the tool name and basic action. It is under-specified.

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

Completeness1/5

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

Given the tool has 4 parameters with no schema descriptions, no annotations, and an output schema, the description is severely incomplete. It does not explain parameter defaults, time range interpretation, or result limits. The agent cannot determine how to use the tool correctly from this description alone.

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

Parameters1/5

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

Schema description coverage is 0%, so the schema does not explain parameter meanings. The description also fails to explain any parameters (e.g., query, earliest_time, latest_time, max_count). The agent is left to infer from parameter names alone, which is inadequate for correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool searches Splunk logs with a query. It is specific about verb and resource, and distinguishes from sibling tools like get_all_users or search_errors by focusing on general search. However, it does not explicitly differentiate from search_errors, which might be a more specialized sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like search_errors. There is no mention of prerequisites, when not to use, or context for choosing this tool over others.

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

Deploy Server