Skip to main content
Glama
ycyun

ABLESTACK MOLD MCP Server

by ycyun

MOLD listApis 메타 조회

mold_listApisMeta

Retrieve API metadata including names, async status, and parameters from the ABLESTACK MOLD MCP Server to understand available cloud infrastructure management capabilities.

Instructions

listApis로부터 API 메타데이터(name, isasync, params)를 조회합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo

Implementation Reference

  • Registers the "mold_listApisMeta" MCP tool, including its input schema and inline handler that fetches and returns API metadata using fetchApisMeta.
    server.registerTool(
      "mold_listApisMeta",
      {
        title: "MOLD listApis 메타 조회",
        description: "listApis로부터 API 메타데이터(name, isasync, params)를 조회합니다.",
        inputSchema: { name: z.string().optional() },
      },
      async ({ name }) => {
        const metas = await fetchApisMeta({ name });
        return { content: [{ type: "text", text: JSON.stringify(metas, null, 2) }] };
      }
    );
  • Core helper function that calls listApis API, parses the response, and extracts metadata (name, description, isasync, params) for APIs matching optional name filter.
    export async function fetchApisMeta({ name } = {}) {
      const data = await callApi("listApis", name ? { name } : {});
      const resp = data.listapisresponse || data.listApisResponse || data.listapis || data;
      const apis = resp.api || resp.apis || resp;
      if (!apis || !Array.isArray(apis)) {
        throw new Error("listApis 응답을 파싱할 수 없습니다. (api 배열 없음)");
      }
      return apis.map((a) => ({
        name: a.name,
        description: a.description,
        isasync: !!a.isasync,
        since: a.since,
        related: a.related,
        params: Array.isArray(a.params)
          ? a.params.map((p) => ({
              name: p.name,
              type: p.type,
              required: !!p.required,
              description: p.description,
              length: p.length,
            }))
          : [],
      }));
    }
  • Tool handler function that invokes fetchApisMeta and formats the result as MCP response.
    async ({ name }) => {
      const metas = await fetchApisMeta({ name });
      return { content: [{ type: "text", text: JSON.stringify(metas, null, 2) }] };
    }
  • Input schema defining optional 'name' parameter using Zod.
    inputSchema: { name: z.string().optional() },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what data is retrieved but doesn't describe how: whether it returns all APIs or filtered results, response format, error conditions, authentication requirements, rate limits, or whether it's a read-only operation. For a metadata retrieval tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise - a single Korean sentence that directly states the tool's function. There's no wasted language, repetition, or unnecessary elaboration. Every word contributes to understanding the tool's purpose.

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

Completeness2/5

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

For a metadata retrieval tool with no annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It doesn't explain what format the metadata returns, how results are structured, whether filtering occurs, or any behavioral characteristics. The agent would struggle to use this tool effectively without additional context.

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 description mentions retrieving metadata from 'listApis' but doesn't explain the single 'name' parameter in the schema. With 0% schema description coverage and one undocumented parameter, the description adds minimal value beyond implying some connection to listApis. However, since there's only one parameter, the baseline is higher than for tools with multiple undocumented parameters.

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 ('조회합니다' - retrieves/retrieves) and resource ('API 메타데이터' - API metadata) with specific fields (name, isasync, params). It distinguishes from siblings by specifying it retrieves metadata from 'listApis' rather than performing operations like calling or configuring. However, it doesn't explicitly differentiate from all siblings (e.g., mold_getConfig might also retrieve configuration metadata).

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, appropriate contexts, or compare to sibling tools like mold_getConfig (which retrieves configuration) or mold_call (which executes APIs). The agent receives no help in selecting this tool over others for metadata retrieval needs.

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