Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Apps

list_apps

List installed Splunk apps with details such as name, label, version, description, author, and visibility. Paginate with offset and filter by search criteria to find specific apps.

Instructions

Retrieve installed Splunk applications including name, label, version, description, author, and visibility. If has_more is true, call again with offset=next_offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoPage size. Default 50. Maximum 200. Values above 200 are capped to 200; 0 uses 50. Do not send a count larger than 200.
offsetNoResult offset (default 0)
search_filterNoSplunk REST search filter (e.g. 'name=*TA*')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.12
    • changedInput schema / properties / count / description
      Previous value: -"Page size 1-200 (default 50)"New value: +"Page size. Default 50. Maximum 200. Values above 200 are capped to 200; 0 uses 50. Do not send a count larger than 200."
  2. Changed3 schema fields changedv0.6.11
    • addedInput schema / properties / count
      Added value: +{
+  "default": 50,
+  "description": "Page size 1-200 (default 50)",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Result offset (default 0)",
+  "type": "integer"
+}
    • addedInput schema / properties / search_filter
      Added value: +{
+  "default": "",
+  "description": "Splunk REST search filter (e.g. 'name=*TA*')",
+  "type": "string"
+}
  3. Changed1 schema field changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses the pagination mechanism and hints at a read-only operation through 'Retrieve', which is useful beyond the schema. It does not mention authentication or side effects, but the operation appears non-mutating and the pagination detail is valuable.

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 with no filler. The main purpose is front-loaded, and the pagination instruction is concise and actionable.

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?

For a simple list operation, the description covers what the tool returns, how to paginate, and the essential usage pattern. The output schema is absent, but the description lists the returned fields sufficiently for an agent to understand the result shape.

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 description coverage is 100%, so the parameters are already fully documented in the input schema. The description adds minimal parameter semantics beyond mentioning offset/next_offset for pagination, so baseline 3 is appropriate.

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 states a specific verb ('Retrieve') and a specific resource ('installed Splunk applications'), and lists the returned fields. This clearly distinguishes it from sibling tools like list_config_files or list_dashboards.

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 gives clear usage guidance by explaining the pagination contract: if has_more is true, call again with offset=next_offset. It does not explicitly discuss alternatives or when-not-to-use, but the domain is specific enough that the intended use is clear.

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

Deploy Server

Other Tools