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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncr_list_images

Read-only

Lists container images in a specified Naver Cloud registry, with pagination, to help you inspect available images and manage deployments.

Instructions

List all container images in a specified registry (GET /repositories/{registry})

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": {
      "registryName": "<registryName>"
    },
    "name": "ncloud_ncr_list_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (sent as 'page', > 0)
pageSizeNoPage size (sent as 'pagesize', > 0)
registryNameYesName of the registry

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.1
    • changedInput schema / properties / pageNo / description
      Previous value: -"Page number for pagination"New value: +"Page number (sent as 'page', > 0)"
    • addedInput schema / properties / pageNo / minimum
      Added value: +1
    • changedInput schema / properties / pageNo / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Page size for pagination"New value: +"Page size (sent as 'pagesize', > 0)"
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
  2. First observedv1.10.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds only the raw endpoint (GET /repositories/{registry}); it says nothing about pagination behavior despite pageNo/pageSize params, nor any rate limits or return shape. Value added beyond annotations is minimal, so a baseline 3.

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?

A single front-loaded sentence with zero filler. It is well-sized, though including an endpoint in parentheses is borderline redundant rather than earning clear value.

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?

For a simple read-only list tool with full schema coverage and a readOnly annotation, the essentials are present, but the absence of any pagination or return-format note (no output schema exists) leaves a small gap for an agent aggregating results.

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%, so the schema already documents registryName, pageNo, and pageSize. The description adds no extra parameter meaning (e.g., default page size or ordering), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('container images') scoped to 'a specified registry', which cleanly separates it from singular siblings like ncloud_ncr_get_image and from ncloud_ncr_list_registries. It does not explicitly name an alternative, so it falls just short of 5.

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?

There is no when-to-use guidance and no alternatives named. An agent must infer from the name alone whether to reach for this versus list_tags, get_image, or get_registry; nothing in the text routes it.

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