Skip to main content
Glama
zhouweico

mcp-kubevela

by zhouweico
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

vela_compare_application

Read-onlyIdempotent

Compare application configurations to diagnose config drift, checking latest vs cluster running state or a specific revision against running or latest.

Instructions

对比应用配置差异（诊断配置漂移）。三种模式：

  • 仅传 env：最新配置 vs 该环境集群运行态

  • 传 revision + compare_with=running：指定版本 vs 集群运行态

  • 传 revision + compare_with=latest：指定版本 vs 最新配置

对应 API：POST /api/v1/applications/{app}/compare

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo环境名。不传 revision 时必填：对比最新配置与该环境集群运行态
app_nameYes应用名称
revisionNo版本号。传入后以该版本为基准做对比
compare_withNorevision 的对比对象：running（集群运行态）或 latest（最新配置）running
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.5.0
    • removedInput schema / $defs / CompareApplicationInput
      Removed value: -{
-  "additionalProperties": false,
-  "description": "对比应用配置差异的输入参数",
-  "properties": {
-    "app_name": {
-      "description": "应用名称",
-      "minLength": 1,
-      "title": "App Name",
-      "type": "string"
-    },
-    "compare_with": {
-      "default": "running",
-      "description": "revision 的对比对象：running（集群运行态）或 latest（最新配置）",
-      "pattern": "^(running|latest)$",
-      "title": "Compare With",
-      "type": "string"
-    },
-    "env": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "环境名。不传 revision 时必填：对比最新配置与该环境集群运行态",
-      "title": "Env"
-    },
-    "response_format": {
-      "$ref": "#/$defs/ResponseFormat",
-      "default": "markdown"
-    },
-    "revision": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "版本号。传入后以该版本为基准做对比",
-      "title": "Revision"
-    }
-  },
-  "required": [
-    "app_name"
-  ],
-  "title": "CompareApplicationInput",
-  "type": "object"
-}
    • addedInput schema / properties / app_name
      Added value: +{
+  "description": "应用名称",
+  "minLength": 1,
+  "title": "App Name",
+  "type": "string"
+}
    • addedInput schema / properties / compare_with
      Added value: +{
+  "default": "running",
+  "description": "revision 的对比对象：running（集群运行态）或 latest（最新配置）",
+  "pattern": "^(running|latest)$",
+  "title": "Compare With",
+  "type": "string"
+}
    • addedInput schema / properties / env
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "环境名。不传 revision 时必填：对比最新配置与该环境集群运行态",
+  "title": "Env"
+}
    • removedInput schema / properties / params
      Removed value: -{
-  "$ref": "#/$defs/CompareApplicationInput"
-}
    • addedInput schema / properties / response_format
      Added value: +{
+  "$ref": "#/$defs/ResponseFormat",
+  "default": "markdown"
+}
    • addedInput schema / properties / revision
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "版本号。传入后以该版本为基准做对比",
+  "title": "Revision"
+}
    • changedInput schema / required
      Previous value: -[
-  "params"
-]New value: +[
+  "app_name"
+]
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false. The description adds behavioral context by explaining the three comparison modes and the underlying API endpoint, which helps the agent understand the tool's side-effect-free nature and how the parameters influence behavior.

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 concise and front-loaded with the primary purpose, followed by a clear bulleted list of modes. Every sentence earns its place, and the API endpoint is provided as a reference. No fluff.

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?

The tool has an output schema, so return format is covered there. The description fully explains the input combinations and the diagnostic purpose, making it complete for an agent to select and invoke correctly. Sibling relationships are not needed since this is a distinct comparison tool.

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 80%, so the baseline is 3. The description goes beyond the schema by synthesizing the parameter combinations (env-only, revision+running, revision+latest), clarifying the interplay between env, revision, and compare_with. This adds meaning beyond the individual parameter descriptions.

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 application configuration differences to diagnose configuration drift, with specific verb and resource. It also details three distinct comparison modes, distinguishing it from other tools in the sibling list that are primarily list/get/query operations.

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?

The description explicitly explains when to use each of the three modes (only env, revision with compare_with=running, revision with compare_with=latest), providing concrete conditions. It does not explicitly mention exclusions or alternative tools, but the mode guidance is clear enough for an agent to decide.

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

Install Server

Other Tools