ncloud-mcp-server

ncloud_gtm_get_policy_resources

Read-only

Retrieve resource details for a Global Traffic Manager policy by policy ID to inspect its configured resources.

Instructions

Get resource details for a specific Global Traffic Manager policy

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": {
      "policyId": "<policyId>"
    },
    "name": "ncloud_gtm_get_policy_resources"
  }
}

Input Schema

Name	Required	Description	Default
`policyId`	Yes	Policy ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The readOnlyHint annotation already declares that this is a safe read operation, so the description does not contradict it. The description adds no additional behavioral context beyond what the annotation provides, but no further disclosure is needed for a straightforward GET 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, front-loaded sentence that efficiently states the tool's purpose without any filler or redundant information. It is appropriately sized for a tool with one parameter.

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

Completeness3/5

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

For a simple read-only tool with one parameter, the description is minimally adequate. However, with no output schema, the agent is not informed about what 'resource details' entails (e.g., which resource types are included), leaving some ambiguity that could be clarified with a short explanation.

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 100% coverage for the single parameter (policyId with description 'Policy ID'), so the description is not required to compensate. The description's reference to 'a specific policy' aligns with the parameter but adds no new semantic information.

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 verb (Get) and resource (resource details for a specific Global Traffic Manager policy), making the tool's purpose immediately understandable. It distinguishes itself from list-oriented tools by specifying 'for a specific... policy', though it does not explicitly differentiate from the sibling tool ncloud_gtm_get_policy_detail.

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?

The description provides no explicit guidance on when to use this tool versus alternatives such as ncloud_gtm_get_policy_detail or ncloud_gtm_get_resource_types. The phrase 'for a specific policy' implies a prerequisite (having a policyId) but no clear context for choosing this tool over siblings.

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

Deploy Server