Skip to main content
Glama
lallen30

BluestoneApps MCP Remote Server

by lallen30

get_theme_example

Retrieve React Native theme code examples from BluestoneApps coding standards to implement consistent styling in mobile applications.

Instructions

Get code for a React Native theme

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
theme_nameYesTheme Name

Implementation Reference

  • Handler function for the get_theme_example tool. It takes theme_name, attempts exact match with getExampleContent, falls back to fuzzy match using findClosestMatch, and returns the code content or error message.
    async ({ theme_name }) => {
      if (!theme_name) {
        return {
          content: [
            {
              type: "text",
              text: "Theme name not specified",
            },
          ],
        };
      }
      
      try {
        // First try exact match
        const result = getExampleContent("theme", theme_name);
        
        if (result.error) {
          // Try to find by fuzzy match
          const themesDir = path.join(CODE_EXAMPLES_DIR, "react-native", "theme");
          const closestMatch = findClosestMatch(themesDir, theme_name);
          
          if (closestMatch) {
            const fuzzyResult = getExampleContent("theme", closestMatch);
            return {
              content: [
                {
                  type: "text",
                  text: fuzzyResult.content?.[0] ?? fuzzyResult.error ?? "Error: No content available",
                },
              ],
            };
          } else {
            return {
              content: [
                {
                  type: "text",
                  text: `Theme ${theme_name} not found`,
                },
              ],
            };
          }
        }
        
        return {
          content: [
            {
              type: "text",
              text: result.content?.[0] ?? result.error ?? "Error: No content available",
            },
          ],
        };
      } catch (err) {
        console.error(`Error getting theme example ${theme_name}:`, err);
        return {
          content: [
            {
              type: "text",
              text: `Error getting theme example: ${err}`,
            },
          ],
        };
      }
    },
  • Zod schema defining the input parameter theme_name as a required string.
    {
      theme_name: z.string().describe("Theme Name"),
    },
  • src/index.ts:514-583 (registration)
    Registration of the get_theme_example tool on the MCP server with name, description, schema, and inline handler function.
    server.tool(
      "get_theme_example",
      "Get code for a React Native theme",
      {
        theme_name: z.string().describe("Theme Name"),
      },
      async ({ theme_name }) => {
        if (!theme_name) {
          return {
            content: [
              {
                type: "text",
                text: "Theme name not specified",
              },
            ],
          };
        }
        
        try {
          // First try exact match
          const result = getExampleContent("theme", theme_name);
          
          if (result.error) {
            // Try to find by fuzzy match
            const themesDir = path.join(CODE_EXAMPLES_DIR, "react-native", "theme");
            const closestMatch = findClosestMatch(themesDir, theme_name);
            
            if (closestMatch) {
              const fuzzyResult = getExampleContent("theme", closestMatch);
              return {
                content: [
                  {
                    type: "text",
                    text: fuzzyResult.content?.[0] ?? fuzzyResult.error ?? "Error: No content available",
                  },
                ],
              };
            } else {
              return {
                content: [
                  {
                    type: "text",
                    text: `Theme ${theme_name} not found`,
                  },
                ],
              };
            }
          }
          
          return {
            content: [
              {
                type: "text",
                text: result.content?.[0] ?? result.error ?? "Error: No content available",
              },
            ],
          };
        } catch (err) {
          console.error(`Error getting theme example ${theme_name}:`, err);
          return {
            content: [
              {
                type: "text",
                text: `Error getting theme example: ${err}`,
              },
            ],
          };
        }
      },
    );
  • Shared helper function to retrieve code content from example files in the specified subcategory directory (e.g., 'theme'), used by get_theme_example and other example tools.
    function getExampleContent(subcategory: string, filename: string): { content?: string[]; path?: string; error?: string } {
      const searchDir = path.join(CODE_EXAMPLES_DIR, "react-native", subcategory);
      
      const filePath = findFileInSubdirectories(searchDir, filename);
      
      if (!filePath || !fs.existsSync(filePath)) {
        return { error: `Example ${filename} not found` };
      }
      
      try {
        const content = fs.readFileSync(filePath, 'utf8');
        return {
          content: [content],
          path: path.relative(BASE_DIR, filePath)
        };
      } catch (err) {
        console.error(`Error reading example ${filename}:`, err);
        return { error: `Error reading example ${filename}` };
      }
    }
  • Shared helper function that performs fuzzy matching to find the closest filename containing the search term in a directory, used for fallback in get_theme_example.
    function findClosestMatch(directory: string, searchName: string, extensions: string[] = ['.js', '.jsx', '.ts', '.tsx']) {
      if (!fs.existsSync(directory)) return null;
      
      let closestMatch = null;
      
      for (const ext of extensions) {
        const files = glob.sync(`${directory}/**/*${ext}`);
        
        for (const filePath of files) {
          const fileName = path.basename(filePath);
          const fileNameNoExt = path.basename(fileName, path.extname(fileName));
          
          if (fileNameNoExt.toLowerCase().includes(searchName.toLowerCase())) {
            closestMatch = fileNameNoExt;
            break;
          }
        }
        
        if (closestMatch) break;
      }
      
      return closestMatch;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get code' but doesn't specify if this is a read-only operation, requires authentication, has rate limits, or what the output format is (e.g., code snippet, file). This leaves significant gaps for a tool that likely returns data.

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?

The description is a single, clear sentence with zero waste, front-loaded with the core action. It's appropriately sized for a simple tool, making it efficient and easy to parse.

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 low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It lacks details on behavioral traits and usage context, which are needed for full understanding, though the concise purpose helps.

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?

The input schema has 100% description coverage, with 'theme_name' documented as 'Theme Name'. The description doesn't add any meaning beyond this, such as examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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 the verb ('Get') and resource ('code for a React Native theme'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'get_component_example' or 'get_hook_example', which follow a similar pattern for different resources, so it lacks explicit distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'list_available_examples' that might help discover themes, there's no mention of prerequisites, context, or exclusions, leaving usage unclear.

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/lallen30/mcp-remote-server'

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