Skip to main content
Glama

classify_lines

Filter log lines to identify interesting entries (errors, security events) and skip routine lines using a trained ML model.

Instructions

Classify log lines as LOOK (interesting) or SKIP (routine) using a trained ML model.

Uses a logistic regression model trained on 17 loghub datasets (345M lines). Lines classified as LOOK include errors, warnings, security events, resource exhaustion, hardware anomalies, and other operationally significant entries.

Args: file_path: Path to the log file to classify. threshold: Probability threshold for LOOK classification (0.0-1.0, default 0.5). Lower values capture more lines but with more false positives. max_lines: Maximum number of lines to process (0 = all lines). max_look_lines: Maximum number of LOOK lines to return in detail (default 200). output: Output format - "summary" for overview stats + sample LOOK lines, "look_only" for all captured LOOK lines with probabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
thresholdNo
max_linesNo
max_look_linesNo
outputNosummary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully shoulders the burden. It details the ML model (logistic regression), training data (17 datasets, 345M lines), and classification criteria. It also explains threshold behavior and output formats, giving a clear picture of behavior.

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

Conciseness4/5

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

The description is well-structured with a clear first sentence followed by a detailed Args section. Every sentence adds value, though the Args list could be more concise. Overall, it is appropriately sized for the complexity.

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?

Given the five parameters, no annotations, and an output schema (though not shown), the description covers the tool's purpose, model, input, and output formats. It is sufficiently complete for an AI agent to select and invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, but the description explains all five parameters: file_path is mandatory, threshold effect is described, max_lines and max_look_lines are clarified, and output two options are detailed. This adds significant meaning beyond the raw schema.

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?

The description clearly states the verb 'classify' and the resource 'log lines', specifying the classification outcome (LOOK vs SKIP). It distinguishes itself from sibling tools like analyze_errors and search_logs by focusing on ML-based binary classification.

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 lacks explicit guidance on when to use this tool versus alternatives. No comparison with siblings like analyze_errors or search_logs is provided, and there are no conditions or prerequisites mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ascii766164696D/log-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server