Skip to main content
Glama

get_setup_guide

Get step-by-step setup instructions for HTML, React, or testing projects that use Modus Web Components. Quickly access configuration guides to start building with the design system.

Instructions

Get setup instructions for HTML or React projects using Modus Web Components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesThe setup type ("html", "react", "testing")

Implementation Reference

  • The getSetupGuide handler function that looks up setup guides by type from the loaded setup data and returns the content as text.
    private async getSetupGuide(type: string): Promise<any> {
      const normalizedType = type.toLowerCase();
      const guide = this.setup.find(
        (s) =>
          s.setupType.toLowerCase() === normalizedType ||
          s.filename.toLowerCase().includes(normalizedType)
      );
    
      if (!guide) {
        const availableTypes = this.setup.map((s) => s.setupType).join(", ");
        return {
          content: [
            {
              type: "text",
              text: `Setup guide type "${type}" not found.\n\nAvailable types: ${availableTypes}`,
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: guide.content,
          },
        ],
      };
    }
  • Schema definition for the get_setup_guide tool, requiring a 'type' string parameter ('html', 'react', 'testing')
    {
      name: "get_setup_guide",
      description:
        "Get setup instructions for HTML or React projects using Modus Web Components.",
      inputSchema: {
        type: "object",
        properties: {
          type: {
            type: "string",
            description: 'The setup type ("html", "react", "testing")',
          },
        },
        required: ["type"],
      },
    },
  • src/index.ts:329-340 (registration)
    Registration of the 'get_setup_guide' tool in the CallToolRequestSchema switch statement, routing to getSetupGuide()
      case "get_setup_guide":
        return await this.getSetupGuide((args?.type as string) || "");
    
      case "get_theme_usage":
        return await this.getThemeUsage();
    
      case "get_development_rules":
        return await this.getDevelopmentRules();
    
      default:
        throw new Error(`Unknown tool: ${name}`);
    }
  • src/index.ts:260-297 (registration)
    Tool listing registration where get_setup_guide is declared as an available tool with its name, description, and input schema
        },
        {
          name: "get_setup_guide",
          description:
            "Get setup instructions for HTML or React projects using Modus Web Components.",
          inputSchema: {
            type: "object",
            properties: {
              type: {
                type: "string",
                description: 'The setup type ("html", "react", "testing")',
              },
            },
            required: ["type"],
          },
        },
        {
          name: "get_theme_usage",
          description:
            "Get theme implementation guidelines and usage instructions.",
          inputSchema: {
            type: "object",
            properties: {},
          },
        },
        {
          name: "get_development_rules",
          description:
            "Get universal development rules and best practices for Modus Web Components.",
          inputSchema: {
            type: "object",
            properties: {},
          },
        },
      ];
    
      return { tools };
    });
  • The loadSetup() helper that reads setup guide markdown files from the setup directory and populates the setup array used by getSetupGuide()
    private loadSetup(): void {
      if (!existsSync(this.setupPath)) {
        console.error(`Setup directory not found at: ${this.setupPath}`);
        console.error("Please run: node download-docs.js");
        return;
      }
    
      const files = readdirSync(this.setupPath).filter((f) => f.endsWith(".md"));
    
      for (const file of files) {
        const content = readFileSync(join(this.setupPath, file), "utf-8");
        let setupType = file.replace(".md", "").replace("setup_", "");
    
        // Map filenames to more user-friendly types
        if (setupType === "universal_rules") setupType = "universal";
        if (setupType === "theme_usage") setupType = "theme";
    
        this.setup.push({
          filename: file,
          setupType,
          content,
        });
      }
    
      console.error(`Loaded ${this.setup.length} setup guide files`);
    }
Behavior2/5

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

No annotations are present, so the description carries full burden. It implies read-only behavior ('Get') but does not explicitly state that the tool has no side effects, requires no authentication, or any other behavioral traits.

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

Conciseness4/5

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

The description is a single, short sentence that is easy to parse. However, it is slightly under-specifying by omitting the 'testing' type, which would have been more accurate.

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 (one parameter, no output schema), the description is mostly adequate. It does not explain the return format or the difference between setup types, but for a basic retrieval tool it meets a minimum viable standard.

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

Parameters2/5

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

With 100% schema coverage, the description adds little value beyond the schema. It redundantly lists 'HTML or React' but fails to mention the 'testing' option, creating a mild inconsistency.

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 identifies the tool's purpose: retrieving setup instructions for HTML or React projects using Modus Web Components. However, it omits the 'testing' type that is valid according to the schema, slightly reducing clarity.

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 guidance is provided on when to use this tool versus its siblings (e.g., get_component_docs, list_all_components). The description does not indicate scenarios or prerequisites.

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/julianoczkowski/mcp-modus'

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