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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_init_scripts

Read-only

List all init scripts in the current region. Supports pagination and filtering by init script numbers.

Instructions

List all init scripts in the current region

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_list_init_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number for pagination
pageSizeNoPage size for pagination
initScriptNoListNoFilter by init script numbers

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?

Annotations include readOnlyHint=true, which matches the description. The description adds the region scoping constraint but does not disclose pagination behaviour or return format. Given the annotation already covers safety, this is acceptable but not rich.

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 ('List all init scripts in the current region') that immediately conveys the action, resource, and scope without any unnecessary 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 list tool with full schema coverage and a readOnlyHint annotation, the description is adequate. However, since there is no output schema, a little more context about the return structure or pagination defaults would improve completeness, but it is not essential.

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 descriptions cover 100% of parameters, including pagination and filtering. The description's phrase 'all' could slightly conflict with the optional initScriptNoList filter, but the schema clarifies this. The description adds no new parameter semantics beyond the schema.

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 'List', a clear resource 'init scripts', and scopes it to 'the current region'. This clearly distinguishes it from sibling tools like ncloud_get_init_script_detail, ncloud_create_init_script, and ncloud_delete_init_scripts.

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 it (to enumerate init scripts in the current region) without mentioning alternatives or exclusions. The context is clear, but it does not explicitly state when not to use it or point to alternatives.

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