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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncr_get_image

Read-only

Get detailed information about a container image in a specified registry, including metadata and configuration, to inspect image details.

Instructions

Get detailed information about a specific container image

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

Input Schema

NameRequiredDescriptionDefault
imageNameYesName of the image to query (e.g. 'hello/world')
registryNameYesName of the registry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and the description aligns with a read operation, so no contradiction. However, the description adds minimal behavioral context beyond the annotation, lacking details about return structure, pagination, or any access requirements.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core purpose instantly and efficiently.

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

Completeness4/5

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

This is a simple get-by-identifier tool with two self-explanatory parameters and a read-only annotation. The description is likely sufficient for invocation, though it does not specify what 'detailed information' contains; this is acceptable for the low complexity level.

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 coverage is 100% with descriptive names and an example for imageName. The description adds no additional parameter 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.

Purpose5/5

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

The description clearly states the action ('Get detailed information') and the resource ('specific container image'). It distinguishes from sibling tools like ncloud_ncr_list_images (list all) and ncloud_ncr_delete_image (delete) by emphasizing a single image lookup.

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?

Use for a single image is implied by the word 'specific', but there is no explicit guidance on when to use this tool versus alternatives, such as ncloud_ncr_list_images for enumeration. No exclusions or prerequisites are mentioned.

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