OpsChugex LocalOps MCP

Overview Schema Source Related Servers Discussions Admin

Software Changes

software_changes

Read-onlyIdempotent

Compare the current installed-software inventory with a caller-supplied baseline to identify added, removed, or changed software without persisting data.

Instructions

Compare the current bounded installed-software inventory with a caller-supplied baseline. The server does not persist a baseline or write to disk.

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": {
      "previousInventory": "<previousInventory>"
    },
    "name": "software_changes"
  }
}

Input Schema

Name	Required	Description	Default
`previousInventory`	Yes

Output Schema

Name	Required	Description	Default
`added`	Yes
`removed`	Yes
`limitation`	Yes
`currentCount`	Yes
`baselineCount`	Yes
`versionChanged`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior beyond that: no baseline persistence and no disk writes, which tells the agent the comparison is stateless and repeatable.

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?

Two sentences, zero padding, with the core comparison stated first and the stateless caveat second. Every sentence carries information.

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?

An output schema exists, so return values need no explanation, and the stateless behavior is disclosed. The gaps are the undocumented input shape (no schema descriptions) and thin guidance on matching semantics (name vs name+version) and behavior at the 500-item limit.

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% and the description only labels the input as a 'caller-supplied baseline'. It omits the array-of-objects structure, the name/version fields, and the 500-item cap that the schema enforces, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (compare) plus resource (current installed-software inventory against a caller-supplied baseline), which is meaningfully distinct from the sibling inventory tools like installed_software and software_versions. It does not name those siblings explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The statement that the server does not persist a baseline implies the caller must retain and supply their own, which is implied usage guidance. However, there is no explicit when-to-use, when-not-to-use, or routing advice versus installed_software / software_versions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.