Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_create_package

Create or update a Cloud Functions package with a unique name, optional description and default parameters. Idempotent PUT operation ensures reliable deployment across platforms.

Instructions

Create or update a Cloud Functions package (PUT — idempotent). Name: 1-50 chars of letters, digits, '-' and '_', must not start with '-', and must be unique across packages/actions/triggers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoPreview the request without calling the API
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
parametersNoDefault parameters as a {key: value} JSON object. Lowest precedence: runtime params > trigger params > action params > package params.
descriptionNoDescription (0-3000 bytes)
packageNameYesName of the package to create or update

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • changedInput schema / properties / description / description
      Previous value: -"Description of the package"New value: +"Description (0-3000 bytes)"
    • addedInput schema / properties / description / maxLength
      Added value: +3000
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": false,
+  "description": "Preview the request without calling the API",
+  "type": "boolean"
+}
    • addedInput schema / properties / packageName / maxLength
      Added value: +50
    • addedInput schema / properties / packageName / minLength
      Added value: +1
    • changedInput schema / properties / parameters / description
      Previous value: -"Default parameters for the package as a JSON object"New value: +"Default parameters as a {key: value} JSON object. Lowest precedence: runtime params > trigger params > action params > package params."
    • changedInput schema / properties / platform / description
      Previous value: -"Platform type (default: vpc)"New value: +"Platform (default: vpc). Singapore/Japan regions support vpc only."
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation is idempotent and that package names must satisfy format and uniqueness requirements. These are useful behavioral details that help the agent anticipate failures and understand that re-running is safe. It does not describe output or side effects, but the annotation already signals no destructive behavior.

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 two sentences with no filler. The core operation and idempotency are front-loaded, followed by the most relevant naming constraints.

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?

The description provides the essential information needed to call the tool correctly: the operation, idempotency, and packageName validation rules. Remaining details like the platform enum and parameter precedence are already fully documented in the schema, so the description does not need to restate them. It is complete enough for an agent selecting and invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all parameters, so the baseline is 3. The description adds value by specifying packageName's allowed character set, length rules, prohibited leading '-', and uniqueness across packages/actions/triggers, which the schema does not fully convey.

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 states a specific verb, 'Create or update', and a specific resource, 'Cloud Functions package', and identifies the HTTP method as PUT. It distinguishes this tool from related siblings like ncloud_functions_get_package, ncloud_functions_delete_package, and ncloud_functions_list_packages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly conveys when to use the tool: whenever creating or updating a Cloud Functions package. It does not explicitly mention alternatives or exclusions, but the resource-scoped naming makes the intended use unambiguous.

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