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

apollo-mcp-server

by iceycn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_items

List configuration items in a namespace with pagination support. Requires Apollo 2.1.0 or later.

Instructions

分页获取 Namespace 下的配置项。需 Apollo 版本>=2.1.0。

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>",
      "env": "<env>",
      "clusterName": "<clusterName>",
      "namespaceName": "<namespaceName>"
    },
    "name": "list_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYes
envYes
clusterNameYes
namespaceNameYes
pageNo页码，默认 0
sizeNo页大小，默认 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

无注释，描述未披露行为特征，如是否只读、是否需要认证、返回格式等。仅提到分页，但对副作用和前提条件无任何说明。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

描述极简，一句完成，但牺牲了关键信息。可以适当扩展而不破坏简洁性，因此评为中等。

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

Completeness1/5

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

6个参数、无输出模式、无注释，描述仅覆盖版本要求和分页概念，未能提供调用该工具所需的完整上下文，如返回格式、错误处理、认证要求等。

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

模式描述覆盖率仅33%（page和size有描述），描述未额外解释必需参数（appId、env、clusterName、namespaceName），导致参数语义严重不足。

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

描述明确说明工具用于分页获取Namespace下的配置项，动词和资源清晰。但未与兄弟工具如'get_item'或'list_namespaces'进行区分，因此略降一分。

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?

描述仅包含版本要求，未提供何时使用此工具而非兄弟工具（如'get_item'获取单个项）的指导，也未说明不适用场景。

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