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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_head_bucket

Read-only

Check if an Ncloud Storage bucket exists and is accessible, returning false on 404. Use ncloud_head_bucket if the bucket may reside in legacy Object Storage.

Instructions

[Ncloud Storage] Check whether a Ncloud Storage bucket exists and is accessible (HEAD /). exists=false on 404. A NoSuchBucket here may mean the bucket lives in the legacy Object Storage instead — try ncloud_head_bucket.

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": {
      "bucketName": "<bucketName>"
    },
    "name": "ncloud_ncs_head_bucket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketNameYesName of the bucket to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4.5/5.0
Behavior4/5

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

While readOnlyHint=true already indicates a safe read operation, the description adds specific behavioral detail: it returns exists=false on 404 and notes the potential fallback scenario. This goes beyond the annotation without contradicting it.

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 sentences, front-loaded with the primary action, and every clause adds value: the HEAD method, the 404 handling, and the alternative tool. No waste.

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

Completeness5/5

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

For a single-parameter, read-only existence check, the description covers the operation, the error semantics, and the alternative path. Nothing essential is missing for an agent to invoke it correctly.

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 only parameter, bucketName, is fully described in the schema with 'Name of the bucket to check'. The description adds no extra semantic nuance, so it meets the baseline for high schema coverage without adding further value.

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 it checks whether a Ncloud Storage bucket exists and is accessible, with a specific verb (check) and resource (bucket). It also distinguishes itself from the legacy Object Storage tool by referencing ncloud_head_bucket, making it easy to differentiate.

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

Usage Guidelines5/5

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

The description explicitly provides a condition for when to use this tool vs the alternative: if a NoSuchBucket error occurs here, it may indicate the bucket is in legacy Object Storage, and the agent should try ncloud_head_bucket. This gives clear when-to-use and when-not-to-use guidance.

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