Skip to main content
Glama
Sign In
splunk-mcp-server

splunk-mcp-server

by balajifunny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_errors

Searches for error logs across specified indexes within a given time range, returning up to a configurable number of results.

Instructions

Search for error logs across indexes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo*
time_rangeNo-1h
max_countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It does not mention that this is a read-only operation, any authentication requirements, rate limits, or potential side effects. The agent has no information beyond a basic search action.

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

Conciseness3/5

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

The description is a single sentence, which is concise. However, it lacks structure (e.g., no example, no parameter hints) and is too minimal to be effective. Every word earns its place, but the description would benefit from at least a second sentence about parameters.

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

Completeness2/5

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

Given the tool's complexity (3 parameters, no annotations) and the presence of an output schema (which is not visible), the description is incomplete. It does not cover parameter behavior, default values, or typical use cases. The agent needs more context to use it correctly.

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%, meaning the JSON schema provides no descriptions for the three parameters (index, max_count, time_range). The description adds no explanation of what these parameters do, leaving the agent to guess their meaning and acceptable values.

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 (search) and resource (error logs) and scope (across indexes). It distinguishes from sibling tools like 'get_log_stats' and 'search_splunk' by specifying error logs, but does not explicitly differentiate from 'search_splunk' which could also search error logs.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'search_splunk' or 'get_log_stats'. There is no mention of context, prerequisites, or restrictions.

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