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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_ddos_event_detail

Read-only

Retrieve detailed information about a specific Anti-DDoS security event using its ticket ID. Designed for Security Monitoring subscribers to investigate DDoS incidents.

Instructions

Get detailed information about a specific Anti-DDoS security event. Only for users subscribed to the Security Monitoring service.

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": {
      "ticketId": "<ticketId>"
    },
    "name": "ncloud_get_ddos_event_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketIdYesThe DDoS event ticket ID to get details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation already declares the operation is read-only. The description adds the subscription eligibility requirement, which is useful, but does not disclose error behavior, required permissions beyond subscription, or return format. With annotation covering the safety profile, a 3 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 two short sentences, front-loaded with the main action, and contains no filler or redundant information.

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 one-parameter read-only detail tool, the description covers purpose and eligibility. No output schema exists, but the tool's return is implied as event details; still, it could mention response structure or error conditions. Given the low complexity, this is reasonably complete.

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 coverage is 100% for the single parameter ticketId, so the schema fully documents its meaning. The description does not add any new parameter semantics beyond what the schema already provides, so the baseline 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 clearly states the tool's action ('Get detailed information') and resource ('specific Anti-DDoS security event'). It distinguishes from sibling list_ddos_events by focusing on a single event detail rather than a list.

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 provides clear context: it retrieves details for a specific event and notes the Security Monitoring subscription requirement. However, it does not explicitly name alternatives like list_ddos_events or state when-not-to-use, but the context is unambiguous.

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