Skip to main content
Glama

ncloud_get_product_price_list

Read-only

Retrieve product and price lists for Naver Cloud Platform Gov with filtering by region, product code, category, and currency, including monthly/hourly rates and discount details via paginated results.

Instructions

Get product and price list. Returns products with their associated pricing information including monthly/hourly rates, conditions, and discount details. Paginated (default 50/page, sorted by productCode); the response includes totalRows/returnedRows/hasMore/nextPageNo (and truncated=true if a single page was size-capped) — follow nextPageNo to page through all results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoNoPage number (default 1). Use nextPageNo from the response to page through results.
pageSizeNoPage size (default 50, max 1000). Results are server-sorted by productCode for stable pagination.
regionCodeYesRegion code (KR, KRS)
detailLevelNo'price' (default): slim response with identity + price fields only (much smaller). 'full': raw payload with all metadata. Tip: for broad category queries combine productCategoryCode + productName to keep responses small.price
productCodeNoProduct code to filter
productNameNoKeyword search (case-insensitive substring). Matches across productName, productDescription, productCode, productType.codeName, productItemKind.codeName — works even when the NCP productName field is empty/Korean (e.g. 'Load Balancer').
payCurrencyCodeNoPayment currency code
productCategoryCodeNoProduct category code (e.g. COMPUTE)
productItemKindCodeNoProduct item kind code (e.g. VSVR)
productItemKindDetailCodeNoProduct item kind detail code (NCP billing classification change, 2026-06-25). Use 'VM' to query VM servers only (otherwise BM may be mixed in), 'BM' for Bare Metal only. Block Storage: BSTAD / BSTBS / BSTBS_BSTAD / CB1 / CB2 / FB1 / FB2.
Behavior4/5

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

With readOnlyHint=true already declared, the description adds useful behavioral context: pagination defaults (50/page, sorted by productCode), response fields (totalRows/returnedRows/hasMore/nextPageNo), and the truncated=true flag behavior. This goes beyond the annotation without contradicting it, though it doesn't mention rate limits or other potential constraints.

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 exceptionally concise, containing just two sentences. It front-loads the purpose and then packs pagination details and response field explanations into the second sentence, with no filler or redundancy.

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?

Despite having no output schema, the description covers the key return fields and pagination mechanics, making it complete for a read-only listing tool. It could have mentioned the required regionCode, but that is already in the schema. Overall, it provides enough context for an agent to use the tool correctly.

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 each parameter already described in detail. The description adds minor context (e.g., sorting by productCode) but does not need to explain parameters. It contributes marginal value beyond the schema, consistent with the baseline for full coverage.

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?

The description clearly states the tool gets a 'product and price list' with specific content (monthly/hourly rates, conditions, discounts). It uses a clear verb+resource structure. However, it does not explicitly differentiate from sibling tools like ncloud_get_product_list or ncloud_get_price_list, though the combined scope is implied by the name and content.

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?

The description provides strong usage guidance on pagination, telling users to 'follow nextPageNo to page through all results' and explaining the default page size and sorting. However, it does not explicitly state when to use this tool vs alternatives (e.g., ncloud_get_price_list), leaving the context implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-gov-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server