Skip to main content
Glama
zhouweico

mcp-kubevela

by zhouweico
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

vela_get_application_manifest

Read-onlyIdempotent

Export an application's YAML manifest as either the latest rendered configuration (source=latest) or the actual running CR (source=running) for GitOps migration, backup, or auditing.

Instructions

导出应用的 Application CR YAML 清单（GitOps 迁移 / 备份 / 审计用）。

source=latest 导出最新渲染配置；source=running 导出集群中实际运行的 CR。 基于 compare 接口的 YAML 字段实现。 对应 API：POST /api/v1/applications/{app}/compare

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envYes环境名
sourceNo导出来源：latest（最新渲染配置）或 running（集群运行态 CR）latest
app_nameYes应用名称

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.5.0
    • removedInput schema / $defs
      Removed value: -{
-  "GetManifestInput": {
-    "additionalProperties": false,
-    "description": "导出应用 YAML 清单的输入参数",
-    "properties": {
-      "app_name": {
-        "description": "应用名称",
-        "minLength": 1,
-        "title": "App Name",
-        "type": "string"
-      },
-      "env": {
-        "description": "环境名",
-        "minLength": 1,
-        "title": "Env",
-        "type": "string"
-      },
-      "source": {
-        "default": "latest",
-        "description": "导出来源：latest（最新渲染配置）或 running（集群运行态 CR）",
-        "pattern": "^(latest|running)$",
-        "title": "Source",
-        "type": "string"
-      }
-    },
-    "required": [
-      "app_name",
-      "env"
-    ],
-    "title": "GetManifestInput",
-    "type": "object"
-  }
-}
    • addedInput schema / properties / app_name
      Added value: +{
+  "description": "应用名称",
+  "minLength": 1,
+  "title": "App Name",
+  "type": "string"
+}
    • addedInput schema / properties / env
      Added value: +{
+  "description": "环境名",
+  "minLength": 1,
+  "title": "Env",
+  "type": "string"
+}
    • removedInput schema / properties / params
      Removed value: -{
-  "$ref": "#/$defs/GetManifestInput"
-}
    • addedInput schema / properties / source
      Added value: +{
+  "default": "latest",
+  "description": "导出来源：latest（最新渲染配置）或 running（集群运行态 CR）",
+  "pattern": "^(latest|running)$",
+  "title": "Source",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "params"
-]New value: +[
+  "app_name",
+  "env"
+]
  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 read-only, idempotent, and non-destructive behavior. The description adds context about the underlying compare API and the difference between latest and running states, which goes beyond what annotations provide. No contradictions found.

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: two sentences plus an API reference. It front-loads the purpose and use cases, then explains source options, with no redundant or filler content.

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 a rich output schema, thorough annotations, and a description covering purpose, use cases, source semantics, and API mapping. Everything needed for correct invocation is present.

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?

All parameters are fully described in the schema (100% coverage), and the description reinforces the meaning of 'source' with concrete semantics (latest vs running). The API reference adds extra clarity, making parameter usage well understood.

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 exports the Application CR YAML manifest, using a specific verb ('导出') and resource ('Application CR YAML 清单'). It distinguishes from siblings like vela_get_application by targeting manifest export for GitOps/backup/audit use cases.

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 provides use cases (GitOps migration/backup/audit) and differentiates between source=latest and source=running. It doesn't explicitly name alternative tools, but the context is clear enough for an agent to know when to choose this tool.

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