Skip to main content
Glama
lallen30

BluestoneApps MCP Remote Server

by lallen30

get_state_management

Retrieve React Native state management standards and guidelines for implementing consistent application state handling.

Instructions

Get state management standards for React Native development

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline asynchronous handler function for the 'get_state_management' tool. It calls the getStandardContent helper to load the state management standards from 'resources/standards/state_management.md' and returns the content (or error) as a text markdown artifact.
    async () => {
      const result = getStandardContent("standards", "state_management");
      
      return {
        content: [
          {
            type: "text",
            text: result.content ?? result.error ?? "Error: No content or error message available",
          },
        ],
      };
    },
  • src/index.ts:207-223 (registration)
    Registration of the 'get_state_management' tool on the MCP server, with no input parameters (empty schema) and an inline handler function that provides React Native state management standards.
    server.tool(
      "get_state_management",
      "Get state management standards for React Native development",
      {},
      async () => {
        const result = getStandardContent("standards", "state_management");
        
        return {
          content: [
            {
              type: "text",
              text: result.content ?? result.error ?? "Error: No content or error message available",
            },
          ],
        };
      },
    );
  • Helper function used by the tool (and others) to read standard content from markdown files in the 'resources/standards' directory. For this tool, it loads 'state_management.md'.
    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 the tool 'gets' standards, implying a read-only operation, but doesn't specify what 'standards' entail (e.g., best practices, library recommendations, patterns), how the information is returned, or any limitations (e.g., scope, format). This leaves significant gaps for a tool with no output schema.

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 with zero waste. It is front-loaded with the core purpose and avoids redundancy. Every word contributes to clarifying the tool's function without extraneous details.

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 'standards' include, the format or structure of the returned information, or any behavioral traits (e.g., if it's static content, requires network access). For a tool with no structured output, more context is needed to guide the agent effectively.

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. A baseline of 4 is given since no parameters exist, and the description doesn't introduce unnecessary complexity.

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 state management standards for React Native development'. It specifies the verb ('Get') and resource ('state management standards') with context ('for React Native development'). However, it doesn't differentiate from siblings like 'get_component_design' or 'get_project_structure' beyond the specific resource type.

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 selecting state management standards, or how it differs from other 'get_' tools that might provide related information. The agent must infer usage from the tool name 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