Skip to main content
Glama
nacos-group

Nacos MCP Server

Official
by nacos-group

list_service_subscribers

Retrieve subscribers for a specified service in Nacos to monitor service dependencies and client connections.

Instructions

This interface retrieves the list of subscribers for a specified service.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoYesThe current page number, default is 1.
pageSizeYesThe size of subscribers in each page, default is 100
namespaceIdNoThe namespaceId of service, default is `public` if missing
groupNameNoThe groupName pattern of service, default is `DEFAULT_GROUP` if missing
serviceNameYesThe serviceName pattern of service, required.
aggregationNoWhether aggregation from whole cluster, if `false`, only get subscribers from requested node, default `true` if missing

Implementation Reference

  • The NacosListServiceSubscribers class implements the tool by defining its name, description, input schema, and the Nacos API endpoint URL used for execution.
    class NacosListServiceSubscribers(NacosTool):
        def __init__(self):
            super().__init__(
                name=NacosToolNames.LIST_SERVICE_SUBSCRIBERS,
                description="This interface retrieves the list of subscribers for a specified service.",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "pageNo": {"type": "int", "description": "The current page number, default is 1."},
                        "pageSize": {"type": "int", "description": "The size of subscribers in each page, default is 100"},
                        "namespaceId": {"type": "string",
                                        "description": "The namespaceId of service, default is `public` if missing"},
                        "groupName": {"type": "string",
                                      "description": "The groupName pattern of service, default is `DEFAULT_GROUP` if missing"},
                        "serviceName": {"type": "string",
                                        "description": "The serviceName pattern of service, required."},
                        "aggregation": {"type": "bool",
                                        "description": "Whether aggregation from whole cluster, if `false`, only get subscribers from requested node, default `true` if missing"}
                    },
                    "required": ["pageNo", "pageSize", "serviceName"],
                },
                url="/nacos/v3/admin/ns/service/subscribers"
            )
  • Tool registration in the MCP server's list_tools decorator, instantiating and returning NacosListServiceSubscribers among other tools.
    @server.list_tools()
    async def handle_list_tools() -> list[types.Tool]:
        """List 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(),
        ]
  • Execution handler in the call_tool function that matches the tool name, retrieves the URL from the tool instance, calls the Nacos server, and returns the result.
    case nacos_tools.NacosToolNames.LIST_SERVICE_SUBSCRIBERS:
        url = nacos_tools.NacosListServiceSubscribers().url
        result = nacos.get(name, url, arguments)
        return [types.TextContent(type="text", text=result)]
  • Enum value defining the exact string name 'list_service_subscribers' for the tool.
    LIST_SERVICE_SUBSCRIBERS = "list_service_subscribers",
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'retrieves' data, implying a read-only operation, but doesn't cover critical aspects like pagination behavior (implied by pageNo/pageSize but not explained), rate limits, authentication needs, or error conditions. This leaves significant gaps for an agent to understand how to interact with it effectively.

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, clear sentence that directly states the tool's purpose without any fluff or redundancy. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every word earns its place.

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 tool's complexity (6 parameters, no output schema, and no annotations), the description is insufficient. It doesn't explain the return format (e.g., structure of subscriber data), pagination details, or error handling. For a tool with multiple parameters and no output schema, more context is needed to guide an agent effectively.

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 input schema has 100% description coverage, so parameters like 'pageNo', 'pageSize', and 'serviceName' are well-documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, such as explaining relationships between parameters or usage examples. 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 subscribers for a specified service'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_service_instances' or 'list_services', which might have overlapping domains but different specific functions.

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. It doesn't mention prerequisites, such as needing the service to exist, or compare it to siblings like 'list_service_instances' for broader context. Usage is implied by the purpose but not explicitly stated.

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