Retrieve log file content from managed AWS, Hetzner, OVH, or custom SSH instances by specifying instance ID, log path, and line count.
Get log file content from any managed instance.
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | Number of lines to retrieve. | |
| log_path | No | Log file path. | /var/log/syslog |
| instance_id | Yes | Instance ID, name, or custom-server name. |
Changes observed during successful MCP inspections.
v2.24.0v2.23.8v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It states 'Get' but does not explicitly indicate read-only nature, permission requirements, error behavior, or side effects. Minimal transparency beyond the verb.
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 one sentence with no wasted words. It is front-loaded with the action and resource. However, it could incorporate more context without significant expansion.
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 3 parameters and no output schema or annotations, the description is too sparse. It omits important context like return format, error handling, and pagination behavior, making it incomplete for safe and accurate tool invocation.
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?
Schema description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it does not clarify parameter relationships or provide examples.
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 uses a specific verb ('Get') and resource ('log file content from any managed instance'). It clearly indicates the tool's functionality, distinguishing it from sibling tools that target CloudWatch or Docker logs.
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 like cloudwatch_get_log_events or docker_logs. The description does not specify context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.