Skip to main content
Glama
lallen30

BluestoneApps MCP Remote Server

by lallen30

get_project_structure

Retrieve standardized React Native project structure guidelines to organize codebases efficiently and maintain consistent development practices.

Instructions

Get project structure standards for React Native development

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:150-166 (registration)
    Registration of the 'get_project_structure' tool, including the inline handler function that fetches and returns the project structure standards from a markdown file using the getStandardContent helper.
    server.tool(
      "get_project_structure",
      "Get project structure standards for React Native development",
      {},
      async () => {
        const result = getStandardContent("standards", "project_structure");
        
        return {
          content: [
            {
              type: "text",
              text: result.content ?? result.error ?? "Error: No content or error message available",
            },
          ],
        };
      },
    );
  • The handler logic for the 'get_project_structure' tool is inline in the registration. It calls getStandardContent to read 'resources/standards/project_structure.md' and returns it as MCP content.
    server.tool(
      "get_project_structure",
      "Get project structure standards for React Native development",
      {},
      async () => {
        const result = getStandardContent("standards", "project_structure");
        
        return {
          content: [
            {
              type: "text",
              text: result.content ?? result.error ?? "Error: No content or error message available",
            },
          ],
        };
      },
    );
  • Helper function getStandardContent used by get_project_structure (and other tools) to read markdown standards files from resources directory.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but doesn't disclose any behavioral traits such as rate limits, authentication needs, response format, or potential side effects. For a tool with no annotations, this is a significant gap in transparency.

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 that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy for an agent to parse quickly. Every part of the sentence earns its place by specifying the domain ('React Native development').

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 complexity (simple read operation with no parameters) and lack of annotations or output schema, the description is minimally adequate. It states what the tool does but doesn't provide enough context for effective use, such as what 'standards' entail or the format of the returned structure. Without output schema, the description should ideally hint at the return type, but it doesn't.

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 doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs without requiring description compensation.

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: 'Get project structure standards for React Native development.' It specifies the verb ('Get') and resource ('project structure standards'), and distinguishes it from siblings by focusing on structural standards rather than examples, components, or APIs. However, it doesn't explicitly differentiate from all siblings (e.g., 'list_available_examples' might overlap in scope).

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 prerequisites, context for usage, or exclusions. For instance, it doesn't clarify if this should be used before implementing components or as a reference during development, leaving the agent to infer usage from the purpose 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