Skip to main content
Glama
lallen30

BluestoneApps MCP Remote Server

by lallen30

get_service_example

Retrieve React Native service examples to implement coding standards and accelerate development with BluestoneApps MCP server.

Instructions

Get a React Native service example

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_nameYesService Name

Implementation Reference

  • src/index.ts:370-439 (registration)
    Registration of the 'get_service_example' tool using server.tool, including name, description, input schema, and inline handler function.
    server.tool(
      "get_service_example",
      "Get a React Native service example",
      {
        service_name: z.string().describe("Service Name"),
      },
      async ({ service_name }) => {
        if (!service_name) {
          return {
            content: [
              {
                type: "text",
                text: "Service name not specified",
              },
            ],
          };
        }
        
        try {
          // First try exact match
          const result = getExampleContent("services", service_name);
          
          if (result.error) {
            // Try to find by fuzzy match
            const servicesDir = path.join(CODE_EXAMPLES_DIR, "react-native", "services");
            const closestMatch = findClosestMatch(servicesDir, service_name);
            
            if (closestMatch) {
              const fuzzyResult = getExampleContent("helper", closestMatch);
              return {
                content: [
                  {
                    type: "text",
                    text: fuzzyResult.content?.[0] ?? fuzzyResult.error ?? "Error: No content available",
                  },
                ],
              };
            } else {
              return {
                content: [
                  {
                    type: "text",
                    text: `Service ${service_name} not found`,
                  },
                ],
              };
            }
          }
          
          return {
            content: [
              {
                type: "text",
                text: result.content?.[0] ?? result.error ?? "Error: No content available",
              },
            ],
          };
        } catch (err) {
          console.error(`Error getting service example ${service_name}:`, err);
          return {
            content: [
              {
                type: "text",
                text: `Error getting service example: ${err}`,
              },
            ],
          };
        }
      },
    );
  • Inline async handler function that executes the tool logic: checks input, attempts exact match with getExampleContent, falls back to fuzzy match using findClosestMatch, returns markdown content or error.
    async ({ service_name }) => {
      if (!service_name) {
        return {
          content: [
            {
              type: "text",
              text: "Service name not specified",
            },
          ],
        };
      }
      
      try {
        // First try exact match
        const result = getExampleContent("services", service_name);
        
        if (result.error) {
          // Try to find by fuzzy match
          const servicesDir = path.join(CODE_EXAMPLES_DIR, "react-native", "services");
          const closestMatch = findClosestMatch(servicesDir, service_name);
          
          if (closestMatch) {
            const fuzzyResult = getExampleContent("helper", closestMatch);
            return {
              content: [
                {
                  type: "text",
                  text: fuzzyResult.content?.[0] ?? fuzzyResult.error ?? "Error: No content available",
                },
              ],
            };
          } else {
            return {
              content: [
                {
                  type: "text",
                  text: `Service ${service_name} not found`,
                },
              ],
            };
          }
        }
        
        return {
          content: [
            {
              type: "text",
              text: result.content?.[0] ?? result.error ?? "Error: No content available",
            },
          ],
        };
      } catch (err) {
        console.error(`Error getting service example ${service_name}:`, err);
        return {
          content: [
            {
              type: "text",
              text: `Error getting service example: ${err}`,
            },
          ],
        };
      }
    },
  • Input schema using Zod: requires 'service_name' as a string.
    {
      service_name: z.string().describe("Service Name"),
    },
  • Shared helper function called by the handler to load example code content from files in resources/code-examples/react-native/{subcategory} directory.
    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 called by the handler for fuzzy matching of service names to available example filenames.
    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 only states what the tool does ('Get a React Native service example') without mentioning any behavioral traits such as whether it's read-only, if it requires authentication, what happens on errors, or the format of the returned example. This is inadequate for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'React Native service example' entails, how it's returned, or any behavioral aspects. For a tool that likely returns code or configuration examples, more context is needed to guide the agent effectively, making this insufficient for the complexity involved.

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 the parameter 'service_name' documented as 'Service Name'. The description doesn't add any meaning beyond this, such as explaining what constitutes a valid service name or providing examples. Since schema coverage is high, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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

Purpose3/5

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

The description states the tool's purpose as 'Get a React Native service example', which includes a verb ('Get') and resource ('React Native service example'), making it clear what it does. However, it doesn't differentiate from sibling tools like 'get_component_example' or 'get_hook_example', which also retrieve examples but for different resource types, leaving the scope somewhat vague.

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 sibling tools like 'get_component_example' and 'list_available_examples', there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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