Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_stop_scanner

Idempotent

Stop a running data catalog scanner by providing catalog ID and scanner ID to halt scanning operations.

Instructions

Stop a running scanner

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "catalogId": "<catalogId>",
      "scannerId": "<scannerId>"
    },
    "name": "ncloud_datacatalog_stop_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
catalogIdYesCatalog ID
scannerIdYesScanner ID to stop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true (idempotent) and destructiveHint=false (not destructive). The description adds no extra behavioral context beyond stating the action. It does not contradict annotations, but does not elaborate on side effects or state changes.

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?

Single sentence, directly front-loaded with the action and resource. Every word is necessary; no wasted verbiage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does not indicate what the tool returns (e.g., success message, scanner state). For a simple mutating action, this is minimally adequate but could be more informative about the result.

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% with 'Catalog ID' and 'Scanner ID to stop'. The tool description adds no additional parameter information, meeting the baseline for complete schema coverage.

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?

Description clearly states 'Stop a running scanner', using a specific verb (stop) and resource (scanner). This directly distinguishes it from sibling tools like ncloud_datacatalog_run_scanner (start) and ncloud_datacatalog_get_scanner (read).

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?

No guidance on when to use this tool versus alternatives, such as when to stop vs. run or get scanner. The description is too minimal to provide context for decision-making.

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