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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_disable_flow_log

Idempotent

Disable FlowLog on a network interface to stop capturing network traffic logs. Use this to halt logging when no longer needed.

Instructions

Disable FlowLog on a network interface. Stops capturing network traffic logs.

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>"
    },
    "name": "ncloud_disable_flow_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkInterfaceNoYesNetwork interface number to disable FlowLog on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations provide idempotentHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral detail by stating that capturing of network traffic logs stops, which goes beyond the annotations and helps the agent understand the effect.

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 short sentences, front-loaded with the action, and contains no redundant or filler content. Every word adds value.

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 single-parameter operation with idempotency and non-destructive annotations, the description adequately covers purpose and effect. There is no output schema, but the operation is straightforward enough that this is acceptable.

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?

The schema fully describes the only parameter, networkInterfaceNo, with 100% coverage. The description does not add additional parameter semantics beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Disable') and resource ('FlowLog on a network interface'), clearly stating what the tool does. It also distinguishes from the sibling 'enable_flow_log' tool by specifying the opposite action and adding the effect 'Stops capturing network traffic logs.'

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 indicates when to use the tool: when you need to disable FlowLog on a network interface. It does not explicitly mention alternatives or exclusions, but the context is clear and the sibling enable tool is obvious from naming.

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