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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_set_file_plugins

Idempotent

Replace the entire file monitoring plugin list for a server instance by supplying the full set of file paths to monitor.

Instructions

Replace the full set of file monitoring plugins for a server instance (sends the entire list).

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": {
      "instanceNo": "<instanceNo>",
      "configList": "<configList>"
    },
    "name": "ncloud_set_file_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoTarget type (default 'vpcserver')
configListYesFull list of file paths to monitor (replaces existing)
instanceNoYesServer instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations by emphasizing that the operation replaces the entire set and sends the whole list, clarifying that the provided configList is authoritative. It does not contradict the idempotentHint or destructiveHint, and it gives the agent a clear understanding that this is a bulk overwrite operation.

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, well-structured sentence that directly states the action and its key nuance. It is front-loaded with the verb 'Replace' and contains no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, the combination of description, schema, and annotations provides all necessary information for correct invocation: purpose, parameter meanings, and safety profile. The absence of an output schema and the clear behavior make this 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?

The input schema already provides descriptions for all three parameters, including that configList is the full list replacing existing. The description's mention of 'sends the entire list' reinforces but does not add new semantics beyond the schema. With full schema coverage, a baseline score of 3 is appropriate.

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 tool's function: replacing the full set of file monitoring plugins for a server instance. The phrase 'full set' and 'sends the entire list' distinguishes it from incremental add/remove operations among its siblings, making purpose very clear.

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 conveys that this tool is for full replacement of the plugin list, implying it should be used when the goal is to overwrite the entire configuration rather than add or remove individual plugins. However, it doesn't explicitly name alternatives like 'add' or 'remove', so it stops short of explicit when-not-to-use guidance.

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