Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

evaluate_boolean_flag

Determine the state of a boolean feature flag by providing namespace, flag key, and entity ID. Integrates with Flipt MCP Server for real-time evaluation and decision-making in applications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNo
entityIdYes
flagKeyYes
namespaceKeyYes

Implementation Reference

  • MCP tool handler for 'evaluate_boolean_flag'. Validates inputs with Zod schema and delegates to FliptClient.evaluateBoolean, returning the response or error.
    server.tool(
      'evaluate_boolean_flag',
      {
        namespaceKey: z.string().min(1),
        flagKey: z.string().min(1),
        entityId: z.string().min(1),
        context: z.record(z.string()).optional(),
      },
      async args => {
        try {
          const response = await fliptClient.evaluateBoolean(
            args.namespaceKey,
            args.flagKey,
            args.entityId,
            args.context
          );
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error: any) {
          console.error('Error evaluating boolean flag:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to evaluate boolean flag: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Input schema (Zod) for the 'evaluate_boolean_flag' tool defining parameters: namespaceKey, flagKey, entityId, and optional context.
    {
      namespaceKey: z.string().min(1),
      flagKey: z.string().min(1),
      entityId: z.string().min(1),
      context: z.record(z.string()).optional(),
    },
  • Helper method in FliptClient that performs the boolean flag evaluation by calling the generated EvaluationServiceApi.
    async evaluateBoolean(
      namespaceKey: string,
      flagKey: string,
      entityId: string,
      context: Record<string, string> = {}
    ) {
      try {
        const response = await this.evaluationApi.evaluateBoolean({
          namespaceKey,
          flagKey,
          entityId,
          context,
        });
        return response;
      } catch (error) {
        console.error('Error evaluating boolean flag:', error);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/flipt-io/mcp-server-flipt'

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