Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_dataforest_get_kerberos_keytab

Read-only

Downloads the Kerberos keytab file for a Data Forest account. Provide an account ID and savePath to write it to disk, or receive base64 inline.

Instructions

Download the Kerberos keytab file for a Data Forest account. The response is a binary file: pass savePath to write it to disk, otherwise it is returned inline as base64 (≤256 KB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAccount unique identifier (Base62-encoded UUID)
savePathNoLocal file path to save the .keytab file to (recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / savePath
      Added value: +{
+  "description": "Local file path to save the .keytab file to (recommended)",
+  "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 safety profile is covered. The description adds genuine behavioral context beyond that: the response is binary, savePath writes it to disk, and inline returns are base64 capped at 256 KB. That is useful operational detail not in the structured fields.

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 tight sentences, front-loaded with the purpose, followed by the response-format detail. No filler; every clause carries 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?

With no output schema present, the description carries the return-format burden and does so: binary file, disk or inline base64 with a size cap. Minor gaps (e.g., error behavior if the keytab does not exist) are not covered, but the essentials for correct invocation are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, which sets a baseline of 3. The description nonetheless clarifies the practical effect of savePath (writes to disk) versus omitting it (inline base64), adding decision-relevant meaning beyond the schema text.

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?

States a specific verb (Download) and resource (Kerberos keytab file for a Data Forest account), which cleanly distinguishes it from the sibling ncloud_dataforest_reset_kerberos_keytab. An agent can identify the operation without opening the schema.

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 description implies usage (fetch the keytab for an account) but gives no explicit when-to-use guidance, no prerequisites, and never names the alternative operation reset_kerberos_keytab. Usage is inferable but not stated.

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