Fetch recent system logs from a UniFi router via SSH to diagnose network problems. Set line count and optional regex filter to focus on relevant events.
Fetch recent system logs from the router via SSH
| Name | Required | Description | Default |
|---|---|---|---|
| lines | No | Number of lines to fetch (default: 50) | |
| filter | No | Optional regex filter |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the behavioral disclosure. It clearly indicates a read-only fetch over SSH, but it omits prerequisites like SSH availability/credentials and does not mention output size, pagination, or failure modes.
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, front-loaded sentence with no filler. Every word contributes to identifying the action, resource, and method.
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?
This is a simple tool with only two optional parameters fully documented in the schema. However, with no output schema and no annotations, the description leaves SSH prerequisites and the exact result format unaddressed; these gaps are noticeable but not critical for a basic log-fetching tool.
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%, and both parameters already have meaningful descriptions. The tool description adds little beyond the word 'recent,' which only loosely relates to the lines parameter, so it does not substantially enhance the schema.
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 a specific action ('Fetch'), a specific resource ('recent system logs from the router'), and the transport ('via SSH'). This is clear and distinguishes it from generic siblings like run_ssh_command.
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?
There is no explicit guidance on when to use this tool versus alternatives such as run_ssh_command or other network getters. The intended use is implied by the name and wording, but no exclusions or selection criteria are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.