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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_wms_set_status

Idempotent

Start or pause a WMS monitoring scenario: set serviceYn to true for start, false for pause.

Instructions

Start or pause a WMS monitoring scenario (serviceYn: true = start, false = pause)

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": {
      "scenarioId": "<scenarioId>",
      "serviceYn": "<serviceYn>"
    },
    "name": "ncloud_wms_set_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYnYestrue = start monitoring, false = pause monitoring
scenarioIdYesScenario ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The description explains the serviceYn parameter's meaning (true=start, false=pause) but adds no extra behavioral context beyond what the annotations already convey (idempotent, non-destructive). It does not contradict the annotations, and for a simple toggle operation this is sufficient.

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 concise sentence that front-loads the action and parameter meaning. Zero wasted words or redundant phrases.

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 two-parameter tool with full schema coverage and no output schema, the description is complete. It explains the core purpose and the key parameter semantics. Slight deduction for not mentioning any prerequisites or side effects of pausing, but given the simplicity this is minor.

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%, and the description repeats the serviceYn meaning already present in the schema. No additional parameter information is provided beyond what the schema already documents, so baseline 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 action (start or pause) and the resource (WMS monitoring scenario), using a specific verb and resource. It also distinguishes this tool from sibling tools that fetch monitoring data or results by focusing on status changes.

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 provides clear context for when to use the tool: to start or pause a WMS monitoring scenario. It doesn't explicitly mention alternatives or exclusions, but the action itself is unambiguous and the siblings are clearly different (e.g., get_monitor, get_results).

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