Skip to main content
Glama
DevCycleHQ-Sandbox

OpenFeature MCP Server

install_openfeature_sdk

Fetch installation prompts and setup instructions for OpenFeature SDKs across multiple programming languages and frameworks to implement feature flag management.

Instructions

Fetch and return OpenFeature install prompt Markdown by guide name. Available guides: android, dotnet, go, ios, java, javascript, nestjs, nodejs, php, python, react, ruby. Input: { guide: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guideYes

Implementation Reference

  • The handler function that executes the tool: parses input for technology and providers, fetches bundled prompt, builds provider-specific instructions, processes the prompt text, logs it, and returns text content with optional resource links.
      async (args: unknown): Promise<CallToolResult> => {
        const { technology, providers } = InstallTechnologyArgsSchema.parse(args);
        const prompt: string = BUNDLED_PROMPTS[technology];
    
        const providerPrompts = buildProviderPrompts(providers, technology);
        const finalText = processPromptWithProviders(
          prompt,
          providers,
          technology,
          providerPrompts
        );
        console.error(`install_openfeature_sdk prompt text: \n${finalText}`);
    
        return {
          content: [
            {
              type: "text" as const,
              text: finalText,
            },
            // Include resource links for any available provider docs so clients can read them directly
            ...buildProviderResourceLinks(providers, technology),
          ],
        };
      }
    );
  • Zod input schema for the tool arguments: requires 'technology' (enum of SDK types) and optional array of 'providers'.
    const InstallTechnologyArgsSchema = z.object({
      technology: InstallTechnologySchema,
      providers: providersSchema.optional().default([]),
    });
  • Exports registerInstallTools function which registers the 'install_openfeature_sdk' tool including name, description, annotations, input schema, and handler.
    export function registerInstallTools(
      registerToolWithErrorHandling: RegisterToolWithErrorHandling
    ): void {
      registerToolWithErrorHandling(
        "install_openfeature_sdk",
        {
          description: [
            "Fetch OpenFeature SDK installation instructions, and follow the instructions to install the OpenFeature SDK.",
            "If you are installing a provider, also fetches the provider installation instructions.",
            "Also includes documentation and examples for using OpenFeature SDK in your application.",
            "Choose the technology that matches the application's language/framework.",
          ].join(" "),
          annotations: {
            title: "Install OpenFeature SDK",
            readOnlyHint: true,
          },
          inputSchema: InstallTechnologyArgsSchema.shape,
        },
        async (args: unknown): Promise<CallToolResult> => {
          const { technology, providers } = InstallTechnologyArgsSchema.parse(args);
          const prompt: string = BUNDLED_PROMPTS[technology];
    
          const providerPrompts = buildProviderPrompts(providers, technology);
          const finalText = processPromptWithProviders(
            prompt,
            providers,
            technology,
            providerPrompts
          );
          console.error(`install_openfeature_sdk prompt text: \n${finalText}`);
    
          return {
            content: [
              {
                type: "text" as const,
                text: finalText,
              },
              // Include resource links for any available provider docs so clients can read them directly
              ...buildProviderResourceLinks(providers, technology),
            ],
          };
        }
      );
    }
  • src/server.ts:72-72 (registration)
    Top-level call to registerInstallTools in the server setup, which triggers registration of the install_openfeature_sdk tool.
    registerInstallTools(registerToolWithErrorHandling);
  • Helper function to process the base prompt with provider-specific instructions, handling marker replacement or appending.
    function processPromptWithProviders(
      prompt: string,
      providers: ProviderName[],
      technology: z.infer<typeof InstallTechnologySchema>,
      providerPrompts: string[]
    ): string {
      // Marker-based injection: replace the block between markers when providers are specified
      const providersMarkerPattern =
        /<!--\s*PROVIDERS:START\s*-->[\s\S]*?<!--\s*PROVIDERS:END\s*-->/;
    
      const providerBlock = providerPrompts.length
        ? ["### Step 2: Provider installation", "", ...providerPrompts].join("\n")
        : "";
    
      const providersAppendix = providerPrompts.length
        ? `\n\n---\n\nProvider installation instructions for ${technology}:\n\n${providerPrompts.join(
            "\n"
          )}`
        : "";
    
      let finalText = prompt;
    
      if (providers.length > 0) {
        if (providersMarkerPattern.test(prompt)) {
          // Replace the marker block with provider content (without the markers)
          finalText = prompt.replace(providersMarkerPattern, providerBlock);
        } else {
          // Fallback: append to the end if no marker exists in the prompt
          finalText = `${prompt}${providersAppendix}`;
        }
      } else {
        // No providers specified: strip the marker block entirely
        finalText = prompt.replace(providersMarkerPattern, "");
      }
    
      return finalText;
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions fetching and returning Markdown, but lacks details on permissions, rate limits, error responses, or whether the operation is read-only or has side effects. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 highly concise and front-loaded, with two sentences that efficiently convey the tool's purpose and input details. Every word serves a purpose, avoiding redundancy or unnecessary elaboration, making it easy to parse 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's low complexity (1 parameter with enum, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and parameter options but lacks details on output format, error handling, or behavioral traits. Without annotations or an output schema, more context on what the Markdown contains or how to handle failures would improve completeness.

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 description adds meaningful context beyond the input schema by listing all available guide options (e.g., android, dotnet, go) and specifying that the input is a guide name. Since the schema description coverage is 0% (no descriptions in schema properties), the description compensates well by clarifying parameter semantics, though it could detail the format or purpose of the returned Markdown more explicitly.

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: 'Fetch and return OpenFeature install prompt Markdown by guide name.' It specifies the verb ('fetch and return'), resource ('OpenFeature install prompt Markdown'), and scope ('by guide name'), making the action concrete. However, since there are no sibling tools mentioned, it cannot differentiate from alternatives, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by listing available guides, suggesting this tool is used to retrieve installation instructions for specific platforms. However, it does not provide explicit guidance on when to use this tool versus alternatives, prerequisites, or error handling. With no sibling tools, the context is limited, but more detailed instructions could enhance clarity.

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/DevCycleHQ-Sandbox/openfeature-mcp'

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