Retrieve the data import history for a Search Engine Service cluster by providing the cluster instance number, with optional paging parameters to access records.
Get data import history 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 readOnlyHint annotation already establishes that this is a safe read operation, and the description's 'Get' wording is consistent with that. However, the description adds little behavioral detail beyond the annotation, such as pagination behavior or whether history is limited to a time window.
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 entire description is one precise sentence with the verb and resource front-loaded. There is no filler, tautology, or redundant restatement of the tool name.
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 list operation, the description, schema, and readOnlyHint together provide enough information to invoke the tool correctly. A note about the exact return fields would be a slight improvement since there is no output schema, but it is not needed for correct invocation.
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?
All three parameters are fully documented in the input schema, including the required serviceGroupInstanceNo as 'Cluster instance number.' The description adds no new parameter-level meaning beyond what the schema already provides.
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 names a specific verb ('Get'), a specific resource ('data import history'), and the target scope ('Search Engine Service cluster'). This clearly distinguishes it from sibling SES tools such as ncloud_ses_run_import and ncloud_ses_get_snapshot_history.
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?
The description gives clear context for when the tool applies—viewing data import history for an SES cluster—but it does not explicitly mention when not to use it or name alternatives. Usage is implied rather than spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.