Skip to main content
Glama
flipt-io

Flipt MCP Server

Official
by flipt-io

create_constraint

Define custom constraints for feature flag segments in Flipt MCP Server by specifying type, property, operator, and value to control targeted evaluations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNo
namespaceKeyYes
operatorYes
propertyYes
segmentKeyYes
typeYes
valueNo

Implementation Reference

  • MCP tool handler for 'create_constraint': calls fliptClient.createConstraint with args, returns JSON stringified response or error message.
    async args => {
      try {
        const response = await fliptClient.createConstraint(
          args.namespaceKey,
          args.segmentKey,
          args.type,
          args.property,
          args.operator,
          args.value,
          args.description
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error: any) {
        console.error('Error creating constraint:', error);
        return {
          content: [
            {
              type: 'text',
              text: `Failed to create constraint: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for the 'create_constraint' tool parameters.
    {
      namespaceKey: z.string().min(1),
      segmentKey: z.string().min(1),
      type: z.enum([
        'STRING_COMPARISON_TYPE',
        'NUMBER_COMPARISON_TYPE',
        'BOOLEAN_COMPARISON_TYPE',
        'DATETIME_COMPARISON_TYPE',
        'ENTITY_ID_COMPARISON_TYPE',
      ]),
      property: z.string().min(1),
      operator: z.string().min(1),
      value: z.string().optional(),
      description: z.string().optional(),
    },
  • src/index.ts:757-808 (registration)
    Registration of the 'create_constraint' MCP tool with server.tool including schema and inline handler.
    server.tool(
      'create_constraint',
      {
        namespaceKey: z.string().min(1),
        segmentKey: z.string().min(1),
        type: z.enum([
          'STRING_COMPARISON_TYPE',
          'NUMBER_COMPARISON_TYPE',
          'BOOLEAN_COMPARISON_TYPE',
          'DATETIME_COMPARISON_TYPE',
          'ENTITY_ID_COMPARISON_TYPE',
        ]),
        property: z.string().min(1),
        operator: z.string().min(1),
        value: z.string().optional(),
        description: z.string().optional(),
      },
      async args => {
        try {
          const response = await fliptClient.createConstraint(
            args.namespaceKey,
            args.segmentKey,
            args.type,
            args.property,
            args.operator,
            args.value,
            args.description
          );
    
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(response, null, 2),
              },
            ],
          };
        } catch (error: any) {
          console.error('Error creating constraint:', error);
          return {
            content: [
              {
                type: 'text',
                text: `Failed to create constraint: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Helper method in FliptClient wrapper that invokes the generated API constraintsApi.createConstraint.
    async createConstraint(
      namespaceKey: string,
      segmentKey: string,
      type: string,
      property: string,
      operator: string,
      value?: string,
      description?: string
    ) {
      try {
        const response = await this.constraintsApi.createConstraint(namespaceKey, segmentKey, {
          type: type as any, // Using 'any' to handle the enum conversion
          property,
          operator,
          value,
          description,
        });
        return response;
      } catch (error) {
        console.error('Error creating constraint:', 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