Retrieve dashboard details for a Search Engine Service cluster using its instance number. Obtain key performance metrics and status to monitor cluster health.
Get dashboard information for a Search Engine Service cluster
| Name | Required | Description | Default |
|---|---|---|---|
| pageNo | No | Page number | |
| pageSize | No | Page size | |
| serviceGroupInstanceNo | Yes | Cluster instance number |
Changes observed during successful MCP inspections.
v1.15.0Input schema / properties / pageNoAdded value: +{
+ "description": "Page number",
+ "type": "number"
+}Input schema / properties / pageSizeAdded value: +{
+ "description": "Page size",
+ "type": "number"
+}v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, and the description adds no behavioral context beyond that—no mention of pagination behavior, output structure, or what 'dashboard information' includes. It does not contradict the annotations, but it also contributes no additional operational disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, succinct sentence with no filler. The action and resource are front-loaded, and every word contributes to identifying what the tool does.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only getter, the description plus schema and annotations are minimally sufficient to invoke the tool correctly. However, with no output schema, the description does not clarify what the returned dashboard information contains or how pagination affects results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so pageNo, pageSize, and serviceGroupInstanceNo are already documented. The description only adds the cluster context and does not clarify relationships between parameters or pagination semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and identifies the resource as a 'Search Engine Service cluster', making the tool's core purpose clear. It does not explicitly differentiate from sibling dashboard tools such as ncloud_list_dashboards or ncloud_ses_get_monitoring, but the SES cluster scoping is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus related SES getters or dashboard-related siblings. The description implies a read-only dashboard retrieval but does not mention prerequisites, alternatives, or a decision context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.