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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_get_scanners

Read-only

Lists scanners within a catalog using optional search and pagination, enabling quick discovery of data scanning tools.

Instructions

Get scanner list in a catalog

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>"
    },
    "name": "ncloud_datacatalog_get_scanners"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
pageSizeNoPage size 1~200 (default: 20)
catalogIdYesCatalog ID
searchValueNoSearch keyword (scanner name or description)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint: true, which already signals safe read behavior. The description adds no additional behavioral context (e.g., pagination, filtering, or return format). It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence front-loading the purpose. Efficient but could be slightly expanded with key constraints like required parameter or scope. No wasted words.

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?

Given no output schema, the description is minimally adequate for a list tool. It could mention that it returns a list of scanners or pagination details. However, parameters are well-documented in the schema.

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?

Input schema has 100% description coverage for all four parameters (catalogId, pageNo, pageSize, searchValue). The description adds no extra meaning beyond what is already in the schema. Baseline score is appropriate.

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 'Get scanner list in a catalog' clearly specifies the action (get), resource (scanner list), and context (in a catalog). It distinguishes from sibling tools like ncloud_datacatalog_get_scanner (single scanner) and ncloud_datacatalog_get_scanner_histories (history data).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like ncloud_datacatalog_get_scanner or ncloud_datacatalog_get_scanner_histories. The description implies it is for listing, but does not state when not to use or provide context for selection.

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