Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_functions_get_action

Read-only

Retrieve a Cloud Functions action definition with source code. Secrets are redacted by default; includeSecrets=true returns raw values when needed.

Instructions

Get an action's full definition including its source code. Secrets found in the code (hard-coded access/secret keys, passwords, tokens, PEM keys) are REDACTED by default and the response carries secretsRedacted=true with the count; pass includeSecrets=true only if you genuinely need the raw values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoPlatform (default: vpc). Singapore/Japan regions support vpc only.vpc
actionNameYesName of the action to retrieve
packageNameNoPackage name ('-' = unpackaged action)-
includeSecretsNoReturn source code unredacted (default false). Even when true, the response still reports how many secret-like values were detected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • addedInput schema / properties / includeSecrets
      Added value: +{
+  "default": false,
+  "description": "Return source code unredacted (default false). Even when true, the response still reports how many secret-like values were detected.",
+  "type": "boolean"
+}
    • addedInput schema / properties / packageName / default
      Added value: +"-"
    • changedInput schema / properties / packageName / description
      Previous value: -"Package name containing the action"New value: +"Package name ('-' = unpackaged action)"
    • changedInput schema / properties / platform / description
      Previous value: -"Platform type (default: vpc)"New value: +"Platform (default: vpc). Singapore/Japan regions support vpc only."
    • changedInput schema / required
      Previous value: -[
-  "packageName",
-  "actionName"
-]New value: +[
+  "actionName"
+]
  2. First observedv1.10.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing redaction behavior: secrets are redacted by default, the response includes secretsRedacted=true with a count, and includeSecrets=true is needed to obtain raw values. This is genuinely useful behavioral context an agent cannot infer from the schema alone.

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?

Two sentences, front-loaded with the primary purpose, and no filler. Every clause contributes useful information, especially the redaction behavior and includeSecrets warning.

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 covers the key return aspects: full definition, source code, secret redaction, and response signal. Since there is no output schema, slightly more detail about other returned fields could help, but the description is sufficient for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics for includeSecrets by explaining the redaction default and the response flag/count, and it adds a usage caution. This goes beyond the schema's already detailed parameter descriptions.

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?

States a specific verb and resource: 'Get an action's full definition including its source code.' This clearly distinguishes the tool from related siblings like list_actions, invoke_action, and get_package by emphasizing the full definition plus source code.

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?

Provides clear context on what the tool returns and practical guidance on when to pass includeSecrets=true ('only if you genuinely need the raw values'). It does not explicitly name alternatives or exclusions, but the purpose is clear enough for basic selection.

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