ncloud-mcp-server

ncloud_get_vpc_peering_detail

Read-only

Retrieve detailed configuration and status of a specific VPC Peering instance by providing its instance number.

Instructions

Get detailed information about a specific VPC Peering instance

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": {
      "vpcPeeringInstanceNo": "<vpcPeeringInstanceNo>"
    },
    "name": "ncloud_get_vpc_peering_detail"
  }
}

Input Schema

Name	Required	Description	Default
`vpcPeeringInstanceNo`	Yes	VPC Peering instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds little behavioral context beyond 'detailed information' and does not mention response structure, pagination, or error behavior. With annotations covering the primary safety trait, a neutral score is appropriate.

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 sentence that is front-loaded with the verb and resource. No filler words, and every word contributes to clarity. It is appropriately sized for a simple get-detail 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?

Given the low complexity (1 parameter, no output schema, readOnly annotation), the description is mostly sufficient. It clearly states the tool's function and required identifier. However, it does not explicitly mention the relationship to list_vpc_peerings or what the returned 'detailed information' includes, which is a minor gap.

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% for the single parameter 'vpcPeeringInstanceNo', which is already described as 'VPC Peering instance number to query'. The tool description does not add extra meaning beyond the schema, so the baseline of 3 applies.

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 ('Get') and resource ('detailed information about a specific VPC Peering instance'), clearly indicating this is a detail-fetch operation for a single peering. It distinguishes from sibling 'list_vpc_peerings' by emphasizing 'specific', making the tool's scope unambiguous.

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 usage is implied: to retrieve details for a known VPC Peering instance number. However, there is no explicit when-to-use advice, mention of prerequisites (e.g., obtaining the instance number from list_vpc_peerings), or exclusion of alternatives. This earns a 'implied usage' score rather than higher.

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

Deploy Server