Skip to main content
Glama
lallen30

BluestoneApps MCP Remote Server

by lallen30

get_component_design

Retrieve React Native component design standards to ensure consistent UI implementation across applications.

Instructions

Get component design standards for React Native development

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:188-204 (registration)
    Registration of the 'get_component_design' tool, including empty input schema and inline async handler that calls getStandardContent to load and return the component design standards from resources/standards/component_design.md
    server.tool(
      "get_component_design",
      "Get component design standards for React Native development",
      {},
      async () => {
        const result = getStandardContent("standards", "component_design");
        
        return {
          content: [
            {
              type: "text",
              text: result.content ?? result.error ?? "Error: No content or error message available",
            },
          ],
        };
      },
    );
  • The handler function for the tool, which fetches the standard content using getStandardContent and formats it as MCP content response.
    async () => {
      const result = getStandardContent("standards", "component_design");
      
      return {
        content: [
          {
            type: "text",
            text: result.content ?? result.error ?? "Error: No content or error message available",
          },
        ],
      };
    },
  • Helper function used by the handler to read the markdown file resources/standards/component_design.md containing the design standards.
    function getStandardContent(category: string, standardId: string): { content?: string; error?: string } {
      const standardPath = path.join(RESOURCES_DIR, category, `${standardId}.md`);
      
      if (!fs.existsSync(standardPath)) {
        return { error: `Standard ${standardId} not found` };
      }
      
      try {
        const content = fs.readFileSync(standardPath, 'utf8');
        return { content };
      } catch (err) {
        console.error(`Error reading standard ${standardId}:`, err);
        return { error: `Error reading standard ${standardId}` };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves standards but doesn't specify whether this is a read-only operation, if it requires authentication, what format the output is in, or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 function without any unnecessary words. It is front-loaded with the core purpose, making it easy to parse and understand quickly.

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 has no parameters and no output schema, the description is minimally adequate by stating what it does. However, it lacks details on behavioral aspects like output format or usage context, which are important for an agent to invoke it correctly, especially with no annotations to supplement.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, aligning with the baseline expectation for tools with no parameters.

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 tool's purpose with a specific verb ('Get') and resource ('component design standards for React Native development'), making it immediately understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'get_component_example' or 'get_theme_example', which might also relate to React Native components.

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. It doesn't mention any prerequisites, context for usage, or how it differs from sibling tools such as 'get_component_example' or 'list_available_examples', leaving the agent to infer usage scenarios.

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