Skip to main content
Glama

devops-linux

server_log_analyze

Analyze Nginx and Apache Combined access logs for HTTP status distribution, error rates, bandwidth, top IPs/endpoints, and suspicious traversal/injection requests.

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": "server_log_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw Nginx or Apache access.log lines.
filePathNo
topLimitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden, and it only lists analysis categories. It does not say whether the tool reads a file off disk (relevant for `filePath`, an access/permission concern), whether there are size or time limits on logs, whether analysis is stateless and non-destructive, or anything about the shape of the result. The enumeration of detected threat categories is mildly informative but is a feature list rather than behavioral disclosure.

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?

A single well-formed sentence that front-loads the verb and resource before the capability list. The list is long but each item names a distinct output, so nothing reads as padding; only the trailing injection/traversal clause slightly crowds the sentence.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only documentation, and it does convey the report contents. The critical omission is input semantics: with zero required parameters, an agent could invoke it with neither `text` nor `filePath` and has no idea what happens. Log size limits and the effect of `topLimit` are likewise absent, which is a meaningful gap for a parsing tool that may receive large inputs.

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

Parameters2/5

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

Schema description coverage is only 33%: `text` is documented, while `filePath` and `topLimit` (default 10) have no schema descriptions. The description compensates for neither — it never explains that `text` and `filePath` are alternative input sources, which one takes precedence, or what `topLimit` bounds (IPs, endpoints, or both).

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 gives a specific verb (analyze) and a precise resource (Nginx and Apache Combined access logs), then enumerates the exact outputs produced: status distribution, error rates, bandwidth, top IPs/endpoints, and suspicious traversal/injection requests. That enumeration makes the tool unmistakable and clearly different in kind from every listed sibling, which covers unrelated domains like binary triage or PDF repair.

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 states what the tool produces but never says when to reach for it, nor does it address the obvious input choice between raw `text` and a `filePath`. There are no exclusions, no preconditions, and no alternatives offered, so an agent gets no routing help beyond the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources