Skip to main content
Glama
Sign In
apollo-mcp-server

apollo-mcp-server

by iceycn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_app_env_clusters

Retrieves environment and cluster information for a specified application ID to understand deployment configurations.

Instructions

获取应用的环境与集群信息。

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": {
      "appId": "<appId>"
    },
    "name": "get_app_env_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes应用 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, and the description lacks behavioral details such as required permissions, rate limits, response structure, or side effects. For a tool with zero annotation coverage, the description provides minimal transparency beyond the basic action.

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 a single, direct sentence that immediately conveys the tool's purpose. It is front-loaded and contains no unnecessary words or fluff.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description should provide more context about what '环境与集群信息' (environment and cluster information) includes. The tool retrieves data, but the agent cannot infer the structure or scope of the response. This lack of completeness limits effective usage.

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?

The single parameter 'appId' is described in the schema as '应用 ID' (App ID). With 100% schema description coverage, the schema already adequately documents the parameter. The tool description does not add additional semantic value beyond what is in the schema, so a baseline score of 3 is appropriate.

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's purpose: '获取应用的环境与集群信息' (get application environment and cluster information). It is a specific verb+resource combination, and the tool name aligns well with this purpose. Among siblings, it is distinct from 'get_cluster' by focusing on an app's environments and clusters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives like 'get_cluster' or 'list_apps', nor does it mention prerequisites or context. This leaves the agent without guidance on selection.

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