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

apollo-mcp-server

by iceycn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_apps

Get a list of applications from Apollo Configuration Center. Optionally filter by app IDs with a comma-separated list; leave empty to retrieve all apps.

Instructions

获取应用列表。可选 appIds 参数（逗号分隔）过滤，为空则返回所有应用。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdsNoappId 列表，逗号分隔，可选

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

Discloses basic behavior (filtering and default listing all apps) but lacks details like pagination, ordering, or any side effects. Since no annotations are provided, the description carries the burden fully, and this is adequate but minimal.

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?

A single sentence that conveys purpose and parameter usage without unnecessary words, perfectly front-loaded.

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?

Given a simple tool with one optional parameter and no output schema, the description fully explains what the tool does and how to use it. No gaps remain.

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?

The schema already describes appIds as a comma-separated list, but the description adds crucial context: leaving it empty returns all apps. This extra behavioral note justifies a slight boost above the baseline of 3.

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 it retrieves a list of applications (获取应用列表), and distinguishes from sibling tools like create_app, get_item, list_items, etc., which have different purposes.

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 explains how to use the optional appIds parameter for filtering and the default behavior when omitted. However, it doesn't explicitly mention when not to use this tool or suggest alternatives.

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