Skip to main content
Glama
Sign In
DeviceLens MCP

DeviceLens MCP

by Dark-Hunt3r1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

devicelens_compare_snapshots

Read-onlyIdempotent

Compare two saved device inventories or a saved snapshot against the live device state to detect changes in Windows hardware configuration.

Instructions

Compare two saved inventories, or compare a saved snapshot with the current live device state.

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": {
      "before": "<before>"
    },
    "name": "devicelens_compare_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNocurrent
beforeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context about comparing two specific snapshots or a snapshot with current state, which is useful behavioral detail beyond the annotations.

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

Conciseness5/5

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

The description is a single sentence that is concise, front-loaded with the verb, and contains no superfluous words.

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

Completeness3/5

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

With 2 parameters, required fields, and an output schema, the description is somewhat incomplete. It does not explain parameter defaults or format, but the core functionality is clear for a simple comparison tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only implicitly suggests that 'before' and 'after' are snapshot identifiers, but does not explain that 'after' defaults to 'current' or the format of the identifiers.

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?

The description clearly states the verb 'compare' and the resources 'saved inventories' and 'current live device state'. It distinguishes from sibling tools like devicelens_capture_snapshot and devicelens_list_snapshots.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool vs alternatives, no prerequisites, and no exclusions or when-not-to-use information.

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