Skip to main content
Glama
nacos-group

Nacos MCP Server

Official
by nacos-group

list_configs

Retrieve and filter configuration lists from a Nacos namespace using pagination, search patterns, and criteria like group, data ID, type, tags, or application name.

Instructions

This interface retrieves the list of configurations under a specified namespace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoYesThe current page number, default is 1.
pageSizeYesThe size of configs in each page, default is 100
namespaceIdNoThe namespaceId of configs, default is `public` if missing
groupNameNoThe groupName pattern of configs, default null means all group. if not null, server will search all config match groupName. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix
dataIdNoThe dataId pattern of configs, default null means all dataId. if not null, server will search all config match dataId. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix
typeNoThe type of configs, default null means all type, if not null, server will search all config match type. Multiple type using `,` to split, such as `text,json`
configTagsNoThe tags of configs, default null means all tags, if not null, server will search all config match tags. Multiple tags using `,` to split, such as `tag1,tag2`
appNameNoThe appName of configs, default null means all appName, if not null, server will search all config match appName.
searchNoThe search way of list configs, default is `blur` means blur search groupName and dataId. Or using `accurate` means accurate match with groupName and dataId.

Implementation Reference

  • Executes the 'list_configs' tool by fetching the Nacos API URL from the tool class and calling the generic NacosServer.get method with the input arguments.
    case nacos_tools.NacosToolNames.LIST_CONFIGS:
        url = nacos_tools.NacosListConfigs().url
        result = nacos.get(name, url, arguments)
        return [types.TextContent(type="text", text=result)]
  • Defines the input schema, description, name, and Nacos API URL for the 'list_configs' tool in the NacosListConfigs class.
    def __init__(self):
        super().__init__(
            name=NacosToolNames.LIST_CONFIGS,
            description="This interface retrieves the list of configurations under a specified namespace.",
            inputSchema={
                "type": "object",
                "properties": {
                    "pageNo": {"type": "int", "description": "The current page number, default is 1."},
                    "pageSize": {"type": "int", "description": "The size of configs in each page, default is 100"},
                    "namespaceId": {"type": "string",
                                    "description": "The namespaceId of configs, default is `public` if missing"},
                    "groupName": {"type": "string",
                                  "description": "The groupName pattern of configs, default null means all group. if not null, server will search all config match groupName. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix"},
                    "dataId": {"type": "string",
                               "description": "The dataId pattern of configs, default null means all dataId. if not null, server will search all config match dataId. If `search=blur`, this parameter allow use `*` to do blur search, such as `*test` to do prefix and `test*` to do suffix"},
                    "type": {"type": "string",
                             "description": "The type of configs, default null means all type, if not null, server will search all config match type. Multiple type using `,` to split, such as `text,json`"},
                    "configTags": {"type": "string",
                                   "description": "The tags of configs, default null means all tags, if not null, server will search all config match tags. Multiple tags using `,` to split, such as `tag1,tag2`"},
                    "appName": {"type": "string",
                                "description": "The appName of configs, default null means all appName, if not null, server will search all config match appName."},
                    "search": {
                        "type": "string",
                        "description": "The search way of list configs, default is `blur` means blur search groupName and dataId. Or using `accurate` means accurate match with groupName and dataId."
                    }
                },
                "required": ["pageNo", "pageSize"],
            },
            url="/nacos/v3/admin/cs/config/list"
        )
  • Registers the 'list_configs' tool (as NacosListConfigs) in the MCP server's list of available tools.
    return [
        nacos_tools.NacosListNamespacesTool(),
        nacos_tools.NacosListServices(),
        nacos_tools.NacosGetService(),
        nacos_tools.NacosListInstances(),
        nacos_tools.NacosListServiceSubscribers(),
        nacos_tools.NacosListConfigs(),
        nacos_tools.NacosGetConfig(),
        nacos_tools.NacosListConfigHistory(),
        nacos_tools.NacosGetConfigHistory(),
        nacos_tools.NacosListConfigListeners(),
        nacos_tools.NacosListListenedConfigs(),
    ]
  • Enum definition for the 'list_configs' tool name used in registration and dispatching.
    LIST_CONFIGS = "list_configs",
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'retrieves' a list, implying a read-only operation. It doesn't disclose behavioral traits such as pagination handling (beyond schema hints), rate limits, authentication needs, error conditions, or what happens with invalid inputs, which are critical for a tool with 9 parameters.

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

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized for a list operation, though it could be more front-loaded with key usage details to improve structure.

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 complexity (9 parameters, no output schema, no annotations), the description is insufficient. It lacks details on return format, pagination behavior, error handling, and how it differs from siblings. For a list tool with rich filtering options, more context is needed to guide effective use.

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 description coverage is 100%, so the schema fully documents all 9 parameters with defaults and behaviors. The description adds no additional parameter semantics beyond implying namespace filtering, which is already covered in the schema. This meets the baseline for high schema coverage.

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?

The description clearly states the action ('retrieves') and resource ('list of configurations under a specified namespace'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_config_history' or 'get_config', which also retrieve configuration-related data, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_config' (for single config) or 'list_config_history' (for historical data). It mentions 'under a specified namespace' but doesn't clarify if this is required or how it relates to other tools, leaving usage context implied at best.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nacos-group/nacos-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server