Skip to main content
Glama
zhouweico

mcp-kubevela

by zhouweico
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

vela_get_app_status

Read-onlyIdempotent

Retrieve KubeVela application status across all environments or for a specific environment. Get an overview or detailed status to monitor deployment health.

Instructions

查看应用运行状态（全部环境概览或指定环境详情）。

对应 API：GET /api/v1/applications/{app}/status GET /api/v1/applications/{app}/envs/{env}/status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo环境名。不填返回所有环境的状态概览
app_nameYes应用名称
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.5.0
    • removedInput schema / $defs / AppStatusInput
      Removed value: -{
-  "additionalProperties": false,
-  "description": "查询应用状态的输入参数",
-  "properties": {
-    "app_name": {
-      "description": "应用名称",
-      "minLength": 1,
-      "title": "App Name",
-      "type": "string"
-    },
-    "env": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "环境名。不填返回所有环境的状态概览",
-      "title": "Env"
-    },
-    "response_format": {
-      "$ref": "#/$defs/ResponseFormat",
-      "default": "markdown"
-    }
-  },
-  "required": [
-    "app_name"
-  ],
-  "title": "AppStatusInput",
-  "type": "object"
-}
    • addedInput schema / properties / app_name
      Added value: +{
+  "description": "应用名称",
+  "minLength": 1,
+  "title": "App Name",
+  "type": "string"
+}
    • addedInput schema / properties / env
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "环境名。不填返回所有环境的状态概览",
+  "title": "Env"
+}
    • removedInput schema / properties / params
      Removed value: -{
-  "$ref": "#/$defs/AppStatusInput"
-}
    • addedInput schema / properties / response_format
      Added value: +{
+  "$ref": "#/$defs/ResponseFormat",
+  "default": "markdown"
+}
    • changedInput schema / required
      Previous value: -[
-  "params"
-]New value: +[
+  "app_name"
+]
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / description
      Added value: +"vela_get_app_status 的结构化输出（status 可为列表或字典）"
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / status
      Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Status"
+}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"vela_get_app_statusOutput"New value: +"GetAppStatusOutput"
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds behavioral nuance by distinguishing between all-environment overview and per-environment detail, and includes the concrete API endpoints that shape expected behavior. It does not go into pagination or error modes, but the extra context is valuable beyond annotations.

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 two short sentences: the first states the purpose and scope, the second lists the API endpoints. Every word earns its place, and the key information is front-loaded. There is no redundancy or filler.

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?

Given that an output schema exists and annotations cover safety, the description is sufficiently complete for a read-only status tool. It clearly defines the two operational modes and maps to APIs. It does not mention authentication or rate limits, but these are not critical for a simple status read. The tool is well-specified overall.

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 67% (app_name and env have descriptions; response_format only has an enum reference). The description does not add parameter details beyond what the schema already provides, and the schema descriptions are adequate. The description's mention of '不填返回所有环境的状态概览' aligns with the schema's env description, but does not enhance it.

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 uses a specific verb '查看' (view) and resource '应用运行状态' (application running status), and further clarifies scope with '全部环境概览或指定环境详情' (all environments overview or specific environment details). This clearly distinguishes it from sibling list tools like vela_list_applications and vela_system_info.

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 implies usage by describing the two modes (overview vs specific env) but does not explicitly state when to prefer this tool over alternatives or provide exclusions. Sibling tools are not referenced, so the guidance is implicit rather than explicit.

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