Skip to main content
Glama
ycyun

ABLESTACK MOLD MCP Server

by ycyun

MOLD 연결정보 설정

mold_setConfig

Configure API endpoint, authentication keys, and signing algorithm for ABLESTACK MOLD MCP Server to enable CloudStack API calls and infrastructure management.

Instructions

endpoint, apiKey, secret 및 서명 알고리즘(sha1|sha256)을 설정합니다. 기본은 sha256. persist=true면 디스크에 저장.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointNo
apiKeyNo
secretNo
algoNo
persistNo

Implementation Reference

  • Handler function for mold_setConfig tool: extracts parameters, calls setConfig helper, returns redacted config as JSON text.
    async ({ endpoint, apiKey, secret, algo, persist = true }) => {
      const info = setConfig({ endpoint, apiKey, secret, algo }, { persist });
      return { content: [{ type: "text", text: JSON.stringify(info, null, 2) }] };
    }
  • Input schema using Zod for validating tool parameters: endpoint, apiKey, secret, algo (sha1/sha256), persist.
    inputSchema: {
      endpoint: z.string().optional(),
      apiKey: z.string().optional(),
      secret: z.string().optional(),
      algo: z.enum(["sha1", "sha256"]).optional(),
      persist: z.boolean().optional(),
    },
  • Registration of the mold_setConfig tool using server.registerTool, including title, description, schema, and handler.
    server.registerTool(
      "mold_setConfig",
      {
        title: "MOLD 연결정보 설정",
        description:
          "endpoint, apiKey, secret 및 서명 알고리즘(sha1|sha256)을 설정합니다. 기본은 sha256. persist=true면 디스크에 저장.",
        inputSchema: {
          endpoint: z.string().optional(),
          apiKey: z.string().optional(),
          secret: z.string().optional(),
          algo: z.enum(["sha1", "sha256"]).optional(),
          persist: z.boolean().optional(),
        },
      },
      async ({ endpoint, apiKey, secret, algo, persist = true }) => {
        const info = setConfig({ endpoint, apiKey, secret, algo }, { persist });
        return { content: [{ type: "text", text: JSON.stringify(info, null, 2) }] };
      }
    );
  • Core setConfig helper: sanitizes inputs, updates global CONFIG state, persists to disk if requested, returns redacted config.
    export function setConfig({ endpoint, apiKey, secret, algo } = {}, { persist = true } = {}) {
      const next = sanitizeConfig({ endpoint, apiKey, secret, algo });
      CONFIG = { ...CONFIG, ...next };
      if (persist) saveConfigToDisk();
      return getConfigRedacted();
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that it sets configuration values, mentions a default algorithm (sha256), and describes persistence behavior ('persist=true면 디스크에 저장' - if persist=true, saves to disk). However, it lacks details on permissions needed, whether it overwrites existing config, error conditions, or rate limits. It adds some behavioral context but is incomplete for a configuration mutation tool.

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 front-loaded and efficiently structured in two sentences: the first states the action and parameters, the second adds behavioral details (default and persistence). Every sentence earns its place with no wasted words, making it appropriately sized for the tool's complexity.

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

Completeness3/5

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

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is partially complete. It covers the action, parameters, and some behavioral traits but lacks details on error handling, return values, or integration with sibling tools. Without annotations or output schema, more context on outcomes and usage scenarios would improve completeness.

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 0%, so the description must compensate. It lists all parameters (endpoint, apiKey, secret, algo, persist) and adds meaning: algo has enum values (sha1|sha256) with a default (sha256), and persist controls disk storage. However, it does not explain the purpose or format of endpoint, apiKey, or secret, leaving gaps in parameter understanding. The description adds value but does not fully compensate for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('설정합니다' - sets/configure) and the specific resources being configured (endpoint, apiKey, secret, and signature algorithm). It distinguishes from siblings like mold_getConfig (which retrieves) and mold_call (which executes calls), though not explicitly named. The purpose is specific but could be more explicit about distinguishing from all siblings.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. It mentions a default (sha256) and persistence behavior, but does not specify prerequisites, when-not-to-use scenarios, or direct comparisons with siblings like mold_getConfig for retrieval. Usage context is implied but not clearly articulated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ycyun/ablestack-MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server