Skip to main content
Glama

get_development_rules

Retrieve universal development rules and best practices for Modus Web Components to ensure consistent code quality and adherence to design system guidelines.

Instructions

Get universal development rules and best practices for Modus Web Components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the get_development_rules tool logic. It looks up a setup guide with setupType === 'universal' or filename containing 'universal' in the loaded setup array, and returns its content as a text response. Returns an error message if not found.
    private async getDevelopmentRules(): Promise<any> {
      const universalGuide = this.setup.find(
        (s) => s.setupType === "universal" || s.filename.includes("universal")
      );
    
      if (!universalGuide) {
        return {
          content: [
            {
              type: "text",
              text: "Universal development rules not found. Please run: node download-docs.js",
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: universalGuide.content,
          },
        ],
      };
    }
  • src/index.ts:285-293 (registration)
    Registration of the tool 'get_development_rules' in the ListToolsRequestSchema handler. Defines the tool name, description ('Get universal development rules and best practices for Modus Web Components.'), and its input schema (empty object - no parameters).
    {
      name: "get_development_rules",
      description:
        "Get universal development rules and best practices for Modus Web Components.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:335-336 (registration)
    Route handler in the CallToolRequestSchema that dispatches to getDevelopmentRules() when the tool name matches 'get_development_rules'.
    case "get_development_rules":
      return await this.getDevelopmentRules();
  • The loadSetup() method that loads setup guide files from the setup directory. It reads .md files and maps filenames to types - specifically, files with 'universal_rules' in the name get type 'universal', which is what getDevelopmentRules() looks up.
    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`);
    }
  • The SetupDoc interface that defines the shape of setup guide objects used by getDevelopmentRules(). It has filename, setupType, and content fields.
    interface SetupDoc {
      filename: string;
      setupType: string;
      content: string;
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the call is read-only, requires authentication, has rate limits, or returns cached data. The term 'Get' implies a read operation, but no further details are given.

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 sentence with no wasted words. It is concise but could be slightly more informative without becoming verbose. Structure is simple and front-loaded.

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 no output schema and no annotations, the description should provide enough context about what the tool returns. It only names the resource but does not describe the return format, structure, or content of 'development rules'. The description is adequate but incomplete.

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?

Input schema has 0 parameters, and schema description coverage is 100%. The description does not add parameter-specific information, but with no parameters, the baseline of 4 is appropriate. No additional semantics are needed.

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?

Description clearly states the verb 'Get' and the resource 'universal development rules and best practices for Modus Web Components'. It distinguishes this tool from siblings like get_design_rules, get_setup_guide, and get_component_docs, which cover different categories.

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 on when to use this tool versus alternatives. Does not mention prerequisites, context, or exclusions. The description merely states what it does without helping the agent decide when to invoke it.

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