Skip to main content
Glama
Verkaka

nacos-config-mcp

by Verkaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Nacos configs

nacos_search_configs
Read-onlyIdempotent

Search or page through Nacos configuration entries in a namespace using filters like dataId, group, app name, tags, and type. Returns paged summaries without content; use nacos_get_config to read a value.

Instructions

Search or page through configuration entries in a namespace. Supports exact and fuzzy matching on dataId, plus filters for group, application name, tags and content type. Returns paged summaries (without content); call nacos_get_config to read a value. Compatible with Nacos 1.x, 2.x and 3.x.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by configuration type, e.g. yaml, properties, json.
groupNoConfiguration group, e.g. DEFAULT_GROUP.
dataIdNoData ID pattern to match. Leave empty to list everything in the namespace.
pageNoNo1-based page number, defaults to 1.
searchNoMatching mode for dataId/group: "accurate" (exact) or "blur" (wildcard). Defaults to blur.
appNameNoFilter by the owning application name.
pageSizeNoItems per page between 1 and 500, defaults to 20.
configTagsNoFilter by configuration tags.
namespaceIdNoNamespace (tenant) ID. Omit to use the namespace configured for this server. The default namespace is "" on Nacos 1.x/2.x and "public" on Nacos 3.x; both are accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable behavioral context by stating the result is a paged summary without content, and by noting compatibility across Nacos major versions, which informs how results and namespace semantics may vary.

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 concise and front-loaded, starting with the core purpose and then layering matching modes, return behavior, routing guidance, and compatibility. Every sentence adds distinct information without redundancy or filler.

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 no output schema, the description efficiently covers what is returned (paged summaries without content), which is essential caller knowledge. Combined with the fully described 9-parameter schema and annotations, the context is complete enough for an agent to use the tool 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?

Schema description coverage is 100%, so the schema already documents every parameter individually. The description adds a high-level view of filters and matching modes, but no significant new parameter-level meaning beyond what the schema provides, justifying the baseline score.

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 searches and pages through configuration entries in a namespace, with specific filters and matching modes. It also distinguishes itself from nacos_get_config by noting it returns summaries without content, making the tool's role unmistakable.

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 gives clear usage context for searching and paging configs, and explicitly directs agents to nacos_get_config when the actual value is needed. It does not, however, contrast itself with the history-related siblings such as nacos_list_config_history, leaving some routing ambiguity for those cases.

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