Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_get_product_price_list

Read-only

Get product pricing information including monthly/hourly rates, conditions, and discounts. Filter by region, product code, or category to find specific pricing details.

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 (e.g. KR, JPN, SGN)
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?

Beyond the readOnlyHint annotation, the description discloses pagination behavior (default page size, sorting, response includes hasMore/nextPageNo, truncated flag), which adds valuable behavioral context. 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.

Conciseness5/5

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

The description is concise at a few sentences, front-loading the main purpose and then efficiently covering pagination behavior. No extraneous content.

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?

The description mentions pricing fields (monthly/hourly rates, conditions, discounts) but does not specify the exact output structure. Given no output schema, more detail on the shape of pricing data would improve completeness. It adequately covers pagination but falls short on output semantics.

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 all parameters. The description does not add significant new meaning beyond a high-level overview. Baseline 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 verb 'Get' and the resource 'product and price list', specifying it returns pricing information including monthly/hourly rates, conditions, and discount details. It is distinct from sibling tools like ncloud_get_product_category_list and ncloud_get_product_list.

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?

The description does not provide guidance on when to use this tool versus alternatives. Sibling tools include similar pricing-related tools (e.g., ncloud_get_price_list, ncloud_get_product_demand_cost_list), but no explicit when/when-not or alternative names are mentioned.

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-mcp-server'

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