Reads recent event records from a Hyper-V guest’s System, Application, Security, or Setup logs with optional event ID and level filters for troubleshooting.
Read recent System, Application, Security, or Setup event records with optional event ID and level filters.
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | ||
| level | No | ||
| vm_name | Yes | ||
| event_id | No | ||
| log_name | No | System | |
| max_events | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'recent' and filterable, but never discloses the actual time window default (72 hours) or the result cap (max_events 30), which are meaningful behavioral traits for an agent deciding whether this query is broad enough.
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?
A single front-loaded sentence with the resource and scope stated first. Efficient, though it spends words enumerating enum values the schema already declares.
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?
An output schema and read-only annotations reduce the burden, but for a 6-parameter tool with zero schema descriptions, the definition omits the required vm_name, the lookback default, and the event cap, leaving an agent to infer how to scope the query.
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 0%, so the description must carry parameter meaning, yet it only gestures at log_name, event_id, and level. The required vm_name, the hours lookback window, and max_events are left entirely unexplained beyond bare titles and defaults.
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?
States a concrete verb (Read) and resource (event records) scoped to guest VM logs, and names the four supported log channels. It does not distinguish itself from the sibling events_snapshot, which an agent could reasonably confuse with it.
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 when-to-use guidance, no exclusions, and no mention of the obvious alternative events_snapshot. The phrase 'recent ... with optional filters' only implies usage rather than directing it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.