Skip to main content
Glama

get_theme_usage

Access theme implementation guidelines and usage instructions for Modus Web Components. Apply consistent theming using design system patterns directly in your IDE.

Instructions

Get theme implementation guidelines and usage instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getThemeUsage() method that handles the 'get_theme_usage' tool. It looks up a setup guide where setupType is 'theme' or filename includes 'theme', and returns its content. Returns an error message if not found.
    private async getThemeUsage(): Promise<any> {
      const themeGuide = this.setup.find(
        (s) => s.setupType === "theme" || s.filename.includes("theme")
      );
    
      if (!themeGuide) {
        return {
          content: [
            {
              type: "text",
              text: "Theme usage guide not found. Please run: node download-docs.js",
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: themeGuide.content,
          },
        ],
      };
    }
  • The tool definition and input schema for 'get_theme_usage'. It has no required input parameters (empty properties object).
    {
      name: "get_theme_usage",
      description:
        "Get theme implementation guidelines and usage instructions.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:332-333 (registration)
    The router case that maps the tool name 'get_theme_usage' to the handler method getThemeUsage().
    case "get_theme_usage":
      return await this.getThemeUsage();
  • The loadSetup() method maps the filename 'setup_theme_usage.md' to setupType 'theme', which is used by getThemeUsage() to find the correct setup guide.
    if (setupType === "universal_rules") setupType = "universal";
    if (setupType === "theme_usage") setupType = "theme";
Behavior2/5

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

No annotations provided; the description does not disclose any behavioral traits beyond the basic operation, such as whether it requires authentication or is read-only.

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, concise sentence that directly states the tool's purpose without unnecessary words.

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 parameters, output schema, or annotations, the description is adequate but lacks details about the format or scope of the returned guidelines.

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?

There are no parameters, and the schema coverage is 100% with an empty schema. The description adds no extra meaning, but the baseline for zero parameters is 4.

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 it retrieves theme implementation guidelines and usage instructions, but does not differentiate from sibling tools like get_component_docs or get_design_rules.

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; usage context is only implied by the name and title.

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