Loki MCP Server

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

The description uses 'Find', which implies a safe read operation, but the annotations declare readOnlyHint=false and destructiveHint=true. This is a significant contradiction: a destructive 'find' operation requires explanation (e.g., if it creates temporary resources or modifies indexes), which is completely absent.

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

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

The single sentence is front-loaded with the verb and contains no waste, but it is inappropriately brief given the tool's complexity, contradictory annotations, and need for sibling differentiation. It sacrifices necessary context for brevity.

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

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

Fails to explain the destructive nature indicated by annotations, lacks differentiation from similar query tools, and provides no guidance on the output format or cardinality (unique series vs. log lines). Incomplete for a tool with 3 parameters and destructive side-effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema adequately documents all three parameters (end, match, start). The description mentions 'matching a selector' which loosely maps to the 'match' parameter, but adds no semantic value beyond the schema's 'Stream selector' description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action ('Find'), resource ('active log stream series'), and system context ('in Loki'). However, 'Find' is slightly weaker than verbs like 'List' or 'Retrieve', and it doesn't explicitly clarify the distinction between 'series' (unique streams) and log lines returned by the sibling 'query' tools.

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

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

Provides no guidance on when to use this tool versus the sibling 'query', 'query_range', 'labels', or 'label_values' tools. In Loki, series discovery and log querying are distinct operations, but the description offers no selection criteria or prerequisites.

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