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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_roles

Read-only

List IAM roles using pagination, search keyword, and column filters to find specific roles quickly.

Instructions

List all IAM roles

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (0-based, default: 0)
sizeNoPage output count (default: 10)
searchWordNoSearch keyword
searchColumnNoSearch column

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes that this is a safe read operation. The description adds the domain (IAM roles) but does not disclose behavioral details such as pagination behavior (i.e., page/size parameters) or that 'all' requires iterating over multiple pages. No contradiction with annotations.

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?

A single, concise sentence with no filler or redundancy. It front-loads the core purpose and is appropriately sized for a simple list tool.

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 straightforward read-only list tool with full schema coverage and a read-only annotation, the description provides adequate context. However, it could benefit from noting that results are paginated via the page/size parameters, which would clarify the scope of 'all'.

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 provides descriptions for all four parameters (page, size, searchWord, searchColumn) with 100% coverage. The description adds no additional parameter semantics, so the baseline 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 'List all IAM roles' uses a specific verb ('List') and a clear resource ('IAM roles'), distinguishing it from sibling tools like ncloud_list_policies and ncloud_list_groups. It fully conveys the tool's function in four words.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or contrasts with other list tools (e.g., list_policies, list_groups), leaving the agent to infer usage from the name alone.

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