Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

web_traffic_summary

Summarize a managed instance's own web access logs for per-vhost request volume, request rate, status-code mix, top client IPs and URLs. Auto-discovers nginx/apache logs when no path is set.

Instructions

Summarize a managed instance's OWN web access logs (X-Forwarded-For / mod_remoteip aware): per-vhost request volume, approx req/s, status-code mix, top client IPs and top URLs. Reads the decisive on-box data that cloudwatch_top_ips (WAF logs only) cannot see. Auto-discovers nginx/apache/httpd logs when log_path is omitted. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoLines to tail per log file (100–200000, default 10000).
top_nNoHow many top IPs/URLs to report (1–100, default 15).
log_pathNoExplicit access-log path. Empty = auto-discover nginx/apache/httpd access logs.
hours_backNoOnly count entries from the last N hours (1–168). Omit for no time filter; the window can never reach further back than the tailed lines cover.
instance_idYesInstance ID or name. '<account>/<name>' picks the server of one provider account; custom servers are 'custom/<name>'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.28.0
    • changedInput schema / properties / instance_id / description
      Previous value: -"Instance ID, name, or custom-server name."New value: +"Instance ID or name. '<account>/<name>' picks the server of one provider account; custom servers are 'custom/<name>'."
  2. Changed1 schema field changedv2.25.0
    • addedInput schema / properties / hours_back
      Added value: +{
+  "description": "Only count entries from the last N hours (1–168). Omit for no time filter; the window can never reach further back than the tailed lines cover.",
+  "type": "integer"
+}
  3. Addedv2.24.0
  4. Removedv2.23.8
  5. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses read-only status, X-Forwarded-For / mod_remoteip awareness, auto-discovery behavior, and the on-box data source, which are useful traits beyond the schema. It does not cover permission or auth requirements.

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?

Four short sentences with no wasted words. The primary purpose and scope are front-loaded, followed by differentiation, auto-discovery behavior, and the read-only safety note.

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 no annotations and no output schema, the description does well to list the summary outputs and explain data sourcing and read-only behavior. It stops short of describing access requirements or any limitations beyond the tailed-line window, but is otherwise complete for a read-only inspection tool.

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 description coverage is 100%, so all five parameters are already documented in the schema. The description adds little parameter-level meaning beyond what the schema provides, which sets the baseline at 3.

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?

States a specific verb and resource: 'Summarize a managed instance's OWN web access logs' with detailed output dimensions (per-vhost volume, req/s, status mix, top IPs/URLs). It also distinguishes itself from the sibling cloudwatch_top_ips by noting the latter sees only WAF logs.

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

Usage Guidelines4/5

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

Names an alternative (cloudwatch_top_ips) and explains the condition that selects this tool: on-box log data that cloudwatch cannot see. Also notes auto-discovery when log_path is omitted. No explicit when-not guidance, but the routing context is clear.

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