Skip to main content
Glama
Sign In
Config Drift Guard MCP

Config Drift Guard MCP

by xiaohuxi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Compare configurations

compare_configs
Read-onlyIdempotent

Compare two local config files to identify configuration drift, classifying added, removed, type, value, and secret changes.

Instructions

Compare two local config files and classify added, removed, type, value, and secret drift.

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": {
      "baselineFile": "<baselineFile>",
      "targetFile": "<targetFile>"
    },
    "name": "compare_configs"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetFileYesAbsolute path to the target config file
baselineFileYesAbsolute path to the baseline config file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds detail on drift types, but doesn't disclose other behaviors like file access scope or error handling.

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?

Single sentence packs key information, but could benefit from a structured breakdown. No wasted words; however, front-loading is adequate.

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 no output schema, description partially explains output (drift types) but lacks details on format. Parameters are well-covered. Sibling tools are listed but no guidance on selection.

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 coverage is 100% with clear parameter descriptions. The description adds the context of comparison and drift classification, but does not provide additional semantic details beyond the schema.

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 tool compares two local config files and classifies drift types (added, removed, type, value, secret). It distinguishes from siblings (scan_secrets, inspect_config) by focusing on comparison and drift classification.

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?

No explicit guidance on when to use this vs alternatives. The usage is implied from the description, but no when-not-to-use or context for choosing between siblings.

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