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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_package

Read-only

Retrieve detailed information about a specific package in Naver Cloud Platform Government Cloud by providing its package name and platform type.

Instructions

Get detailed information about a specific package

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": {
      "packageName": "<packageName>"
    },
    "name": "ncloud_functions_get_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoPlatform type (default: vpc)vpc
packageNameYesName of the package to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

The readOnlyHint annotation indicates a safe read operation, and the description's 'Get' aligns with that. However, the description adds no behavioral context beyond the annotation—no mention of response structure, error cases (e.g., package not found), or rate limits.

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 unnecessary words. It conveys the action and target clearly.

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 operation with two documented params and readOnlyHint annotation, the description is mostly adequate. However, with no output schema, it doesn't clarify what 'detailed information' includes or what happens if the package doesn't exist.

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?

Both parameters (platform and packageName) are fully described in the schema (100% coverage), so the description doesn't need to restate them. The description itself adds no additional parameter semantics beyond what the schema already provides.

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 uses a specific verb ('Get') with a clear resource ('detailed information about a specific package'). It clearly indicates this tool retrieves a single package's details, though it doesn't explicitly contrast with sibling ncloud_functions_list_packages which lists packages.

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?

No guidance is provided on when to use this tool versus alternatives like ncloud_functions_list_packages or when a package name is needed. There are no usage scenarios, prerequisites, or exclusions 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