Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_get_object

Read-only

Retrieve an object from Ncloud Storage as text, with optional version ID and byte range. For DEEP_ARCHIVE objects, restore them first to avoid InvalidObjectState errors.

Instructions

[Ncloud Storage] Download an object from a Ncloud Storage bucket as text (GET /{key}). Supports a specific versionId and a byte Range. A DEEP_ARCHIVE object must be restored first (ncloud_ncs_restore_object) or the call fails with InvalidObjectState.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesObject key (path) to retrieve
rangeNoByte range to fetch, e.g. 'bytes=0-1023'
versionIdNoVersion ID of the object (versioning-enabled buckets). Omit for the current version
bucketNameYesName of the Ncloud Storage bucket

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Name of the bucket"New value: +"Name of the Ncloud Storage bucket"
    • addedInput schema / properties / range
      Added value: +{
+  "description": "Byte range to fetch, e.g. 'bytes=0-1023'",
+  "type": "string"
+}
    • addedInput schema / properties / versionId
      Added value: +{
+  "description": "Version ID of the object (versioning-enabled buckets). Omit for the current version",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, so the read-only nature is known. The description adds valuable behavioral context: returns content as text, and fails with InvalidObjectState if a DEEP_ARCHIVE object hasn't been restored. This goes beyond the annotation and helps the agent anticipate failure modes.

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?

Two sentences, no filler. The primary action is front-loaded, followed by key optional capabilities and the critical failure condition. Every clause earns its place; the archive-restore note is essential and compact.

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 operation, the description covers the essential behavioral aspects: what it returns (text), what parameters it supports, and the one significant failure mode. The lack of an output schema is mitigated by the 'as text' note. It doesn't mention pagination or size limits, but those are unlikely for a single object download.

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 descriptive text for all four parameters (bucketName, key, range, versionId) with 100% coverage. The description reinforces that versionId and Range are supported but adds no new semantic details beyond what the schema offers. Per the baseline rule, 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 downloads an object from a bucket as text, with the specific HTTP verb and resource path (GET /{key}). It distinguishes from siblings like head_object (metadata only) and get_object_attributes by focusing on content retrieval. The mention of versionId and Range support further clarifies scope.

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?

It provides clear context: supports versionId and byte Range, and explicitly notes the prerequisite for DEEP_ARCHIVE objects (must restore first) with a specific alternative tool name. It doesn't explicitly contrast with head_object, but the verb 'download' and 'as text' make the purpose unambiguous among ncs_* tools.

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