Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Sources

list_sources

List data sources from a Splunk index with paginated results. Use offset to fetch additional pages when more sources exist.

Instructions

Discover data sources using the metadata command. Sources can be numerous; results are paged. If has_more is true, call again with offset=next_offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoPage size. Default 50. Maximum 100. Values above 100 are capped to 100; 0 uses 50. Do not send a count larger than 100.
indexNoLimit to one index
offsetNoResult offset (default 0)

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-100 (default 50)"New value: +"Page size. Default 50. Maximum 100. Values above 100 are capped to 100; 0 uses 50. Do not send a count larger than 100."
  2. Changed3 schema fields changedv0.6.11
    • addedInput schema / properties / count
      Added value: +{
+  "default": 50,
+  "description": "Page size 1-100 (default 50)",
+  "type": "integer"
+}
    • addedInput schema / properties / index
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Limit to one index"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Result offset (default 0)",
+  "type": "integer"
+}
  3. Changed1 schema field changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly discloses paging behavior (has_more, offset), which is valuable, but does not state the read-only nature, permissions, or the format of returned data. For a discovery tool this is adequate but not comprehensive.

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?

The description is three concise sentences with no fluff. The purpose is front-loaded, and the pagination logic is stated directly and usefully. Every sentence earns its place.

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

Completeness3/5

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

For a simple 3-parameter optional tool, the description covers the main non-obvious behavior (pagination). However, it does not define what a 'data source' is, describe the response items, or outline any safety aspects, and there is no output schema to compensate. The description is adequate but leaves open questions.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining how to use offset for pagination ('call again with offset=next_offset') and implies count/offset interplay, which is not fully spelled out in the parameter descriptions.

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?

The description states a specific verb and resource ('Discover data sources') and hints at the underlying mechanism ('metadata command'). However, it does not explicitly differentiate from sibling tools like list_indexes or list_sourcetypes, which overlap in scope.

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

Usage Guidelines3/5

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

The description gives clear pagination instructions ('If has_more is true, call again with offset=next_offset') but provides no guidance on when to use this tool versus alternatives such as list_indexes or list_sourcetypes. No exclusions or when-not conditions are mentioned.

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