Featureflip

Official

by canopy-labs

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Flag status across environments

flag_status

Read-only

Check a feature flag's enabled state, targeting strategy, default variation, and prerequisites across environments to compare rollout status.

Instructions

Compact cross-environment view of one flag: enabled state, strategy, default variation, and prerequisites per environment.

Input Schema

Name	Required	Description	Default
`flag`	Yes	Flag key or id
`project`	Yes	Project key

Output Schema

Name	Required	Description	Default
`key`	Yes
`name`	Yes
`type`	Yes
`archived`	Yes
`updatedAt`	Yes
`environments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.0Oct 18, 2026

addedInput schema / properties / flag / description
```
Added value: +"Flag key or id"
```
addedInput schema / properties / project / description
```
Added value: +"Project key"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "type": "boolean"
+    },
+    "environments": {
+      "items": {
+        "properties": {
+          "defaultVariation": {
+            "description": "Variation key served on fallthrough",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "enabled": {
+            "type": "boolean"
+          },
+          "environment": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "prerequisites": {
+            "type": "array"
+          },
+          "strategy": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "key": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updatedAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "key",
+    "name",
+    "type",
+    "archived",
+    "updatedAt",
+    "environments"
+  ],
+  "type": "object"
+}

First observedv0.1.6Sep 16, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful detail that the view is 'compact' and lists which facets are returned, but says nothing about auth requirements, environment coverage limits, or pagination behavior.

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

Conciseness4/5

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

A single tight sentence that front-loads the scope ('cross-environment view') before enumerating returned fields. No wasted words, though it is a sentence fragment rather than full prose.

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

Completeness4/5

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

With an output schema present, return values need no elaboration, and the readOnly annotation covers safety. Parameters are fully described in the schema, so the description is nearly complete; only routing guidance versus get_flag is missing.

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

Parameters3/5

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

Schema description coverage is 100% (both 'flag' and 'project' documented), so the baseline is 3. The description adds no format or identifier-syntax detail beyond what the schema already provides.

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?

States a specific resource (one flag) and a specific scope (cross-environment), with the returned facets named: enabled state, strategy, default variation, prerequisites. This distinguishes it from the single-environment get_flag sibling, though it never names that sibling explicitly.

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 phrase 'cross-environment view of one flag' implies the use case (comparing a single flag's configuration across environments), but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_flag or update_flag_environment_config.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.