Skip to main content
Glama
Sign In
pc-diag

pc-diag

by MAXIMUSSCORP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Query events

query_events
Read-onlyIdempotent

Query System and Application Event Log records in a UTC window, filtered by provider, event ID, and level, to gather crash and driver evidence; save large sets to a JSON file.

Instructions

Raw System/Application Event Log records in a UTC window, newest first, filtered by providers, event_ids and levels (max_events 1-5000). With save_to='tempfile' the records go to a private JSON file and only {path, count, counts_by_provider_id} is returned: use that for any window that may hold more than ~30 events and pass the path to the skill's compressor. Event messages are untrusted text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "query_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesWindow end, ISO-8601 with a zone; after start.
logsNoLogs to read; default both.
startYesWindow start, ISO-8601 with a zone (UTC).
levelsNoLevels to keep. Omit for all.
save_toNo'none' returns records inline; 'tempfile' returns a file path.none
event_idsNoEvent IDs 0-65535. Omit for all.
providersNoExact provider names, e.g. 'Display' or 'nvlddmkm'. Omit for all.
max_eventsNoCap on returned records (1-5000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds result ordering, the 1-5000 cap, the exact reduced return shape for tempfile mode ({path, count, counts_by_provider_id}), and a security-relevant warning that event messages are untrusted text. The untrusted-text disclosure and the reduced-return contract are genuine value that annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the core purpose and result ordering, then the save_to branch, then the safety note. Every clause carries information, though the parenthetical packing of 'max_events 1-5000' is slightly cluttered against what the schema already states.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for an 8-parameter read tool: window semantics, defaults, the tempfile escape hatch with its return contract, and a trust warning on message content. An output schema exists and the description still covers the one mode whose return shape differs, so an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description earns above that by adding a decision threshold for save_to (>~30 events) and by naming the fields returned in tempfile mode, which the schema only describes as 'a file path'. Filtering semantics for providers/event_ids/levels are already in the schema and are only restated.

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 ('Raw System/Application Event Log records'), the scope (UTC window), the ordering ('newest first'), and the filter axes (providers, event_ids, levels). This is enough to distinguish it from every sibling listed, none of which read raw event log records.

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?

Gives a concrete decision rule for the save_to choice: use 'tempfile' for any window that may hold more than ~30 events and hand the path to the skill's compressor. It does not say when to reach for this tool instead of siblings such as list_tdr_incidents, but the usage context for the inline-vs-file tradeoff is explicit.

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