nginx_logsRead Nginx error and access logs to identify server issues and monitor request activity. Supplies log content for infrastructure diagnostics and analysis.
Чтение error и access логов Nginx
| Name | Required | Description | Default |
|---|---|---|---|
| params | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. 'Reading' implies a read-only operation, but it doesn't disclose any side effects, authentication requirements, rate limits, or how logs are retrieved. This is insufficient for an agent to understand the tool's behavior.
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 description is a single short sentence, which is concise, but it provides minimal value. It lacks structure and doesn't front-load any useful details beyond the basic action.
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?
Given that the tool reads Nginx logs and has an output schema, the description is incomplete. It doesn't explain how to specify log types, time ranges, or any filtering options. An agent cannot correctly invoke this tool without further information.
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?
The input schema has a single 'params' object with additionalProperties allowed, but no parameter documentation. The description doesn't mention any parameters, leaving the agent without any guidance on what to pass. Schema coverage is 0%, and the description fails to compensate.
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?
The description states the action (reading) and resource (Nginx error and access logs), which is specific and distinguishes it from nginx_status or nginx_config. However, it doesn't explicitly contrast with other log tools like log_search or linux_logs, so it's not fully differentiating.
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?
No guidance is provided on when to use this tool versus alternatives such as log_search, log_tail, or linux_logs. The description implies it's for Nginx logs specifically, but there are no conditions or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.