Stop an active data import job on a Search Engine Service cluster to halt the process and prevent further resource usage. Provide the cluster instance number to cancel the running import.
Stop the running data import job on a Search Engine Service cluster
| Name | Required | Description | Default |
|---|---|---|---|
| serviceGroupInstanceNo | Yes | Cluster instance number |
Changes observed during successful MCP inspections.
v1.15.0Input schema / properties / importTaskIdRemoved value: -{
- "description": "Import task ID to stop",
- "type": "string"
-}Input schema / requiredPrevious value: -[
- "serviceGroupInstanceNo",
- "importTaskId"
-]New value: +[
+ "serviceGroupInstanceNo"
+]v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds the fact that it targets a 'running' job, which is useful context, but does not disclose whether the job can be resumed, partial data impact, or response behavior. With annotations present, this is adequate but not rich.
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?
A single, clear sentence with no fluff. The action and target are front-loaded, making it immediately scannable for an agent.
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 stop action with one parameter, the description is largely complete. It lacks explicit notes on prerequisites (e.g., job must be running) and does not specify return values, but given the low complexity and existing annotations, the gap is minor.
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 coverage is 100% and the parameter 'serviceGroupInstanceNo' is described as 'Cluster instance number'. The description does not add any additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.
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 clearly states a specific verb ('stop'), resource ('data import job on a Search Engine Service cluster'), and implies it applies to a running job. It distinguishes itself from sibling tools like ncloud_ses_run_import and ncloud_ses_get_import_history by focusing on the stopping action.
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 implies usage (when you have a running import job to stop) but does not explicitly state when to use it versus alternatives or provide any exclusions. It lacks guidance on prerequisites or consequences, so an agent must infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.