Skip to main content
Glama
loaditoutadmin

loaditout-mcp-server

Official

install_batch

Install up to 20 specific skills by slug in a single call. Returns install configs for found skills and lists any invalid slugs.

Instructions

Install multiple specific skills in a single call. Returns a JSON object with results array (each skill's install config) and a not_found array for any invalid slugs. Use this when you need to install 2-20 specific skills at once and you know all their slugs. Do not use this for curated collections (use install_pack instead). Maximum 20 skills per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugsYesArray of skill slugs in owner/repo format. Maximum 20.
agentYesTarget agent platform

Implementation Reference

  • The handler function that executes the install_batch tool logic. It takes an array of skill slugs and an agent name, POSTs them to /install-batch API endpoint, and returns the JSON result.
    async function handleInstallBatch(args: {
      slugs: string[];
      agent: string;
    }): Promise<string> {
      const body = {
        slugs: args.slugs,
        agent: args.agent,
      };
    
      const result = await postJSON(`${API_BASE}/install-batch`, body);
      return JSON.stringify(result, null, 2);
    }
  • The tool definition and input schema for install_batch. It requires 'slugs' (array of strings, max 20 skill slugs) and 'agent' (enum of target platforms).
    {
      name: "install_batch",
      description:
        "Install multiple skills at once. Returns install configs for all requested skills in a single call.",
      inputSchema: {
        type: "object" as const,
        properties: {
          slugs: {
            type: "array",
            items: { type: "string" },
            description:
              "Array of skill slugs in owner/repo format. Maximum 20.",
          },
          agent: {
            type: "string",
            enum: ["claude-code", "cursor", "codex-cli", "windsurf", "generic"],
            description: "Target agent platform",
          },
        },
        required: ["slugs", "agent"],
      },
    },
  • The case statement in the tool dispatch switch that routes the 'install_batch' tool name to handleInstallBatch with proper type casting.
    case "install_batch":
      resultText = await handleInstallBatch(
        toolArgs as { slugs: string[]; agent: string }
      );
      break;
  • The postJSON helper function used by handleInstallBatch to make the POST request to the API endpoint.
    function postJSON(url: string, body: Record<string, unknown>, extraHeaders?: Record<string, string>): Promise<unknown> {
      return new Promise((resolve, reject) => {
        const payload = JSON.stringify(body);
        const parsed = new URL(url);
        const options = {
          hostname: parsed.hostname,
          port: parsed.port || 443,
          path: parsed.pathname + parsed.search,
          method: "POST",
          headers: {
            "Content-Type": "application/json",
            "Content-Length": Buffer.byteLength(payload),
            "User-Agent": `loaditout-mcp/${SERVER_VERSION}`,
            ...extraHeaders,
          },
        };
    
        const req = https.request(options, (res) => {
          let data = "";
          res.on("data", (chunk: string) => (data += chunk));
          res.on("end", () => {
            try {
              resolve(JSON.parse(data));
            } catch {
              resolve({ status: res.statusCode });
            }
          });
        });
    
        req.on("error", reject);
        req.write(payload);
        req.end();
Behavior4/5

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

No annotations provided, so description carries the full burden. It discloses the JSON response structure with results and not_found arrays and imposes a 20-skill limit. However, it does not mention whether installation is idempotent or overwrites existing configs.

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?

Three concise sentences, front-loaded with purpose, followed by return info and usage guidance. No unnecessary words or repetition.

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

Completeness5/5

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

Given only 2 parameters, 100% schema coverage, no output schema, the description fully covers purpose, response format, constraints, and alternatives. Agent has sufficient information to decide and invoke correctly.

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?

Input schema already has 100% coverage with clear descriptions for both parameters (slugs, agent). The description restates the 20-skill limit but adds no additional semantic value beyond what the schema provides.

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?

Clearly states 'Install multiple specific skills in a single call.' Distinguishes from siblings like install_pack (curated collections) and install_skill (single skill) by explicitly naming the alternative usage.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('when you need to install 2-20 specific skills at once and you know all their slugs') and when-not-to-use ('Do not use this for curated collections – use install_pack instead'). Also states maximum of 20 skills.

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/loaditoutadmin/loaditout-mcp-server'

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