Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Lookup Files

list_lookup_files

List CSV lookup files in Splunk to reveal metadata like name, owner, app, permissions, and last updated time, helping you locate relevant lookup tables for further analysis.

Instructions

List CSV lookup table files in Splunk. Returns metadata including name, filename, app, owner, sharing/permissions, and last updated time. Use this to discover available lookup files. To view the actual CSV content, use run_splunk_search with '| inputlookup '.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoFilter by app context. Default: '-' (all apps)-
countNoPage size. Default 50. Maximum 200. Values above 200 are capped to 200; 0 uses 50. Do not send a count larger than 200.
ownerNoFilter by owner. Default: 'nobody' (all users)nobody
offsetNoResult offset for pagination. Default: 0
search_filterNoFilter results (e.g., 'name=*geo*')

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). If has_more, use offset=next_offset"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. Changed1 schema field changedv0.6.11
    • changedInput schema / properties / count / description
      Previous value: -"Max results to return. 0=all, default: 50 for performance"New value: +"Page size 1-200 (default 50). If has_more, use offset=next_offset"
  3. Changed5 schema fields changedv0.6.1
    • addedInput schema / properties / app / description
      Added value: +"Filter by app context. Default: '-' (all apps)"
    • addedInput schema / properties / count / description
      Added value: +"Max results to return. 0=all, default: 50 for performance"
    • addedInput schema / properties / offset / description
      Added value: +"Result offset for pagination. Default: 0"
    • addedInput schema / properties / owner / description
      Added value: +"Filter by owner. Default: 'nobody' (all users)"
    • addedInput schema / properties / search_filter / description
      Added value: +"Filter results (e.g., 'name=*geo*')"
  4. Changed1 schema field changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
  5. First observedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states that only metadata is returned and points to run_splunk_search for content, which is the key boundary an agent needs to know. It does not discuss permissions or pagination limits, but the metadata-versus-content distinction is well covered.

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?

Four short, purposeful sentences. The core operation is front-loaded, followed by the return field list, a direct use-case statement, and an alternative tool redirect. No wasted words or redundant schema content.

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?

The description covers purpose, return metadata, and the main content-reading alternative, while the input schema handles all parameter details. It does not explicitly contrast with list_lookup_definitions, but 'CSV lookup table files' and the listed filename field make the distinction sufficiently clear.

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%, and each parameter already has a clear description in the input schema. The tool description adds no parameter-level detail beyond what the schema provides, so it meets the baseline but does not exceed it.

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?

States a specific verb and resource: 'List CSV lookup table files in Splunk' and enumerates the returned metadata fields. The wording 'CSV lookup table files' cleanly distinguishes it from sibling list_lookup_definitions, and the redirect to run_splunk_search clarifies it is not a content-reading tool.

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?

Provides explicit usage guidance: 'Use this to discover available lookup files.' It also names the alternative when the actual CSV content is needed ('use run_splunk_search with inputlookup'), giving clear when-to-use versus when-to-use-another guidance.

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