Skip to main content
Glama
kokushin

exia-scenario-generator MCP Server

by kokushin

setupExia

Initialize the scenario generator to create 'Kotonoha Sisters Explainer' style scenarios for the exia novel game engine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'setupExia' tool. It calls exiaManager.setup() and returns a success or error message.
    server.tool("setupExia", {}, async () => {
      try {
        // exiaのセットアップ
        await exiaManager.setup();
    
        return {
          content: [
            {
              type: "text",
              text: "exiaのセットアップが完了しました。",
            },
          ],
        };
      } catch (error) {
        console.error("Error setting up exia:", error);
        return {
          content: [
            {
              type: "text",
              text: `exiaのセットアップに失敗しました: ${error}`,
            },
          ],
          isError: true,
        };
      }
    });
  • src/server.ts:59-84 (registration)
    Registration of the 'setupExia' tool on the MCP server with empty input schema and inline handler.
    server.tool("setupExia", {}, async () => {
      try {
        // exiaのセットアップ
        await exiaManager.setup();
    
        return {
          content: [
            {
              type: "text",
              text: "exiaのセットアップが完了しました。",
            },
          ],
        };
      } catch (error) {
        console.error("Error setting up exia:", error);
        return {
          content: [
            {
              type: "text",
              text: `exiaのセットアップに失敗しました: ${error}`,
            },
          ],
          isError: true,
        };
      }
    });
  • The core setup logic in ExiaManager: checks if already setup, clones the exia repo from GitHub, and runs npm install.
    async setup(): Promise<void> {
      if (await this.checkSetup()) {
        console.error("exia is already set up.");
        this.isSetup = true;
        return;
      }
    
      console.error("Setting up exia...");
    
      try {
        // GitHubからexiaをクローン
        await execAsync(`git clone https://github.com/kokushin/exia.git ${this.exiaPath}`);
    
        // 必要なパッケージをインストール
        await execAsync("npm install", { cwd: this.exiaPath });
    
        this.isSetup = true;
        console.error("exia setup completed.");
      } catch (error) {
        console.error("Error setting up exia:", error);
        throw new Error("Failed to set up exia");
      }
    }
  • Helper method to check if exia is already set up by verifying directory and package.json existence.
    async checkSetup(): Promise<boolean> {
      try {
        return fs.existsSync(this.exiaPath) && fs.existsSync(path.join(this.exiaPath, "package.json"));
      } catch (error) {
        console.error("Error checking exia setup:", error);
        return false;
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no 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/kokushin/exia-mcp'

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