Skip to main content
Glama
deslicer

MCP Server for Splunk

by deslicer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Lookup Definitions

list_lookup_definitions

Get Splunk lookup definitions (transforms) with metadata for filename, fields, and permissions to see how CSV or external lookups are used in searches.

Instructions

List lookup definitions (transforms) in Splunk. Returns metadata including name, type, associated filename, fields configuration, app, owner, and permissions. Lookup definitions specify how CSV files or external lookups are used in searches.

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., 'filename=*.csv')

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., 'filename=*.csv')"
  4. Changed1 schema field changedv0.5.1
    • addedInput schema / additionalProperties
      Added value: +false
  5. First observedv0.5.0

TDQS

B3.4/5.0
Behavior3/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 transparently describes the return contents and implies a read-only listing operation, but it does not explicitly state that no modifications occur or describe any pagination, permissions, or auth considerations beyond what the schema already shows.

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 tightly written in three sentences: the action and resource are front-loaded, the returned metadata is summarized concisely, and the closing sentence adds valuable domain context. There is no redundant or filler 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 sufficiently explains what the tool returns and what lookup definitions are, which matters because there is no output schema. Combined with a fully documented input schema, an agent has the essential information to call the tool, though a note about the relationship to lookups files would improve completeness.

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 coverage is 100%, with all five parameters already described in the input schema. The description adds no parameter-specific meaning; it only provides general context about lookup definitions, so the baseline of 3 is appropriate.

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 clearly states the action ('List') and resource ('lookup definitions (transforms) in Splunk') and enumerates the returned metadata. It does not explicitly differentiate from the similar sibling list_lookup_files, though mentioning transforms and associated filenames provides some distinction.

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?

There is no guidance on when to use this tool versus alternatives such as list_lookup_files or other list_* tools. The description explains what lookup definitions are, but it does not state when this tool is the right choice or when another sibling should be used.

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