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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncr_list_images

Read-only

List all container images in a specified registry with optional pagination. Specify the registry name to retrieve image details, and use page and pageSize for efficient browsing.

Instructions

List all container images in a specified 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
pageNoPage number (must be > 0)
pageSizeNoPage size (must be > 0)
registryNameYesName of the registry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

The description aligns with the readOnlyHint annotation (list is a read operation) and adds the scope of 'specified registry.' However, it doesn't disclose pagination behavior or the response format, and the word 'all' could be misleading given page/pageSize parameters.

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?

A single 10-word sentence, front-loaded with the verb and resource. It is concise and contains no filler, while still conveying the core purpose.

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 list tool with full schema coverage and a read-only annotation, the description is mostly adequate. However, it omits details about pagination and return values, which is notable because there is no output 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?

The input schema has 100% coverage with each parameter described (page, pageSize, registryName). The description adds no extra parameter meaning beyond naming the registry, so the baseline of 3 applies.

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 uses the specific verb 'List' and identifies the resource as 'container images' with the scope 'in a specified registry,' clearly distinguishing it from siblings like ncloud_ncr_list_registries and ncloud_ncr_get_image.

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 when-to-use or alternative guidance is provided. The usage is implied by the tool name and description, but it doesn't tell the agent when to prefer this over similar listing tools like ncloud_ncr_list_tags or ncloud_ncr_list_registries.

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