ncloud-gov-mcp-server

ncloud_resource_list_groups

Read-only

List resource groups with optional name filter and pagination. Use it to locate groups by name or browse through available groups.

Instructions

List resource groups with optional name filter and pagination.

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_resource_list_groups"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default 0)
`size`	No	Page size (default 20)
`groupName`	No	Group name filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already indicates this is a safe read operation, and the description's 'List' action aligns with that. However, the description adds no behavioral context beyond the annotation, such as pagination behavior details or return format, so it provides minimal added transparency.

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 immediately states the tool's purpose and key capabilities. It is front-loaded and contains no filler, making it easy for an agent to parse quickly.

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 read-only list tool, this description is largely complete: it states the action, resource, and optional parameters. The absence of an output schema is acceptable for a list operation, and the low complexity means the description does not need to explain much beyond what is provided.

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 has 100% description coverage, with each parameter clearly documented (page, size, groupName). The description simply mentions 'name filter and pagination' without adding further context beyond what the schema already provides. The schema carries the semantic weight, so the description adds little extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists resource groups with optional name filtering and pagination. It uses a specific verb and resource, which distinguishes it from most other tools in the sibling list, though it does not explicitly differentiate from similar tools like ncloud_list_groups.

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 the tool is used when you need to list resource groups, but it provides no explicit guidance on when to use it versus alternatives or any exclusions. There is no mention of when not to use it or what other tools might be better suited for related tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server