Skip to main content
Glama
ycyun

ABLESTACK MOLD MCP Server

by ycyun

MOLD 연결정보 조회

mold_getConfig

Retrieve current endpoint, API key, algorithm, and configuration file path for the ABLESTACK MOLD MCP Server to verify and manage API settings.

Instructions

현재 사용 중인 endpoint/apiKey(마스킹)/알고리즘/구성파일 경로를 반환합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registers the 'mold_getConfig' MCP tool, defining its title, description, empty input schema, and a simple handler that returns the redacted configuration as JSON.
    server.registerTool(
      "mold_getConfig",
      {
        title: "MOLD 연결정보 조회",
        description: "현재 사용 중인 endpoint/apiKey(마스킹)/알고리즘/구성파일 경로를 반환합니다.",
        inputSchema: {},
      },
      async () => {
        return { content: [{ type: "text", text: JSON.stringify(getConfigRedacted(), null, 2) }] };
      }
    );
  • The handler function for the tool, which calls getConfigRedacted() and returns the result as a formatted text response.
    async () => {
      return { content: [{ type: "text", text: JSON.stringify(getConfigRedacted(), null, 2) }] };
    }
  • Tool schema definition with Korean title and description, and empty inputSchema indicating no parameters required.
    {
      title: "MOLD 연결정보 조회",
      description: "현재 사용 중인 endpoint/apiKey(마스킹)/알고리즘/구성파일 경로를 반환합니다.",
      inputSchema: {},
    },
  • Helper function that provides a redacted view of the MOLD configuration (endpoint, masked apiKey, secret presence, algorithm, config file path).
    export function getConfigRedacted() {
      const redact = (s = "") => {
        if (!s) return "";
        if (s.length <= 8) return "*".repeat(s.length);
        return s.slice(0, 4) + "***" + s.slice(-4);
      };
      return {
        endpoint: CONFIG.endpoint || "",
        apiKey: redact(CONFIG.apiKey),
        hasSecret: !!CONFIG.secret,
        algo: CONFIG.algo,
        configFile: CONFIG_FILE,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns current configuration details, implying a read-only operation, but doesn't clarify if this requires authentication, has rate limits, or what happens if no configuration is set. The description is minimal and lacks behavioral context beyond the basic purpose.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded with the core action and resources, making it easy for an agent to parse and understand quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate for a basic read operation. However, it lacks details on authentication requirements, error handling, or output format specifics, which could be helpful for an agent. It meets minimum viability but has clear gaps in contextual information.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which aligns with the schema. A baseline of 4 is applied as it correctly handles the absence of parameters without unnecessary elaboration.

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 specific action ('returns') and the exact resources (endpoint, apiKey, algorithm, configuration file path) that are retrieved. It distinguishes itself from siblings like mold_setConfig (which sets configuration) by focusing on retrieval rather than modification.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active connection), exclusions, or comparisons to siblings like mold_listApisMeta, leaving the agent to infer usage context solely from the tool name and description.

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