Skip to main content
Glama
Sign In
oxidized-mcp

oxidized-mcp

by mhajder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Diff Node Versions

diff_node_versions
Read-onlyIdempotent

Compare two configuration versions for a network node and return a unified diff, or show the most recent change when no versions are specified.

Instructions

Show what changed in a node's configuration between two versions.

Returns a unified diff from 'base_oid' (older) to 'oid' (newer). With no arguments besides the node it shows the most recent change.

Input Schema

NameRequiredDescriptionDefault
oidNoNewer version oid (full or prefix); defaults to the latest version
nodeYesNode name or IP address (e.g. 'core-sw01')
groupNoNode group; looked up automatically when omitted
offsetNoZero-based first diff line to return
base_oidNoOlder version oid to compare against; defaults to the version before 'oid'
max_linesNoMaximum diff lines to return (0 = whole diff)
context_linesNoUnchanged lines of context around each change

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Zero-based first diff line to return",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive safety. The description adds meaningful context beyond that: the output is a unified diff and the default no-argument behavior surfaces the most recent change. It doesn't cover rate limits or auth, but the safety profile is already handled.

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, front-loaded with the core purpose, then the diff direction and default behavior. No wasted words.

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

Completeness4/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 not be re-explained, and annotations cover the safety profile. The description supplies the diff direction and default behavior, leaving only sibling routing unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 7 parameters. The description reinforces the base_oid→oid comparison direction, but adds little beyond what the schema fields already state. Baseline 3 applies.

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 (diff/show what changed) and resource (a node's configuration between two versions), and clarifies the return is a unified diff. An agent can distinguish this from get_node_version or list_node_versions, which do not compute differences.

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 description explains default behavior (no arguments shows the most recent change) but never states when to prefer this over siblings like get_node_version or list_node_versions. Usage is implied rather than explicit, with no exclusions.

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