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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_enable_flow_log

Idempotent

Enable FlowLog on a network interface to capture network traffic logs and store them in a specified bucket for analysis and monitoring.

Instructions

Enable FlowLog on a network interface. Captures network traffic logs and stores them in the specified bucket.

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": {
      "networkInterfaceNo": "<networkInterfaceNo>",
      "flowLogBucketName": "<flowLogBucketName>"
    },
    "name": "ncloud_enable_flow_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowLogBucketNameYesObject Storage bucket name to store FlowLog data
networkInterfaceNoYesNetwork interface number to enable FlowLog on
flowLogStatusTypeCodeNoFlowLog status type code (ACCEPT, REJECT, ALL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already mark the operation as idempotent and non-destructive. The description adds context by explaining the effect (captures and stores logs) but does not disclose prerequisites (e.g., bucket must exist) or behavior for repeated calls beyond what the idempotentHint implies. It is not misleading but adds limited behavioral detail.

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 extremely concise: two sentences, no redundancy. It front-loads the primary action and directly states the purpose and outcome, with zero filler words.

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?

For a simple configuration tool with full schema coverage and good annotations, the description provides sufficient context: it explains what the tool does, what it affects, and where logs are stored. It does not mention prerequisites or optional parameter behavior, but these are covered by the schema and the simplicity of the operation makes the description reasonably complete.

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 all three parameters are documented with clear descriptions. The description merely restates 'specified bucket' and 'network interface' without adding new meaning or clarifying the optional flowLogStatusTypeCode parameter or its default behavior. This aligns with the baseline of 3 for high schema coverage.

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 specific action ('Enable FlowLog') and the target resource ('network interface'), and it explains the effect (captures network traffic logs and stores them in a bucket). This distinguishes it from sibling tools like ncloud_disable_flow_log and ncloud_get_flow_log_config.

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 implies when to use the tool (to enable FlowLog) but does not explicitly explain when not to use it or mention alternatives such as disable_flow_log or get_flow_log_config. No clear exclusions or alternative guidance are provided, so the agent must infer usage from the name and description.

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