Skip to main content
Glama
canopy-labs

Featureflip

Official
by canopy-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Archive feature flag

archive_flag
Destructive

Archive a feature flag to stop serving it in evaluations; the change is reversible. If live flags depend on it, archive those dependents first.

Instructions

Archive a flag (soft-hide, evaluation stops serving it). Reversible with restore_flag. Archive dependents first: refused with FLAG_HAS_DEPENDENTS while another live flag lists this one as a prerequisite, so archive those flags (blockedBy in find_stale_flags / list_removal_candidates) first. Refused with FLAG_RECENTLY_EVALUATED while live traffic is still evaluating the flag, because archiving makes every caller fall back to its own hardcoded default — normally that means the code removal has merged but not deployed yet, and the refusal clears itself once it has.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flagYes
forceNoArchive even though traffic is still evaluating the flag. Only for clients that can never be updated (old mobile app versions), where traffic will never drain on its own.
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Archive even though traffic is still evaluating the flag. Only for clients that can never be updated (old mobile app versions), where traffic will never drain on its own.",
+  "type": "boolean"
+}
  2. First observedv0.1.6

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the destructiveHint annotation by naming two refusal codes (FLAG_HAS_DEPENDENTS, FLAG_RECENTLY_EVALUATED), explaining the fallback-to-hardcoded-default consequence, and noting the refusal self-clears after deploy. Minor tension with destructiveHint=true, since the description stresses reversibility, but soft-hide + restore_flag makes this defensible rather than contradictory.

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?

Dense but front-loaded: purpose first, then prerequisites, then refusal conditions. Every sentence carries operational information; it is long only because the failure modes genuinely require explanation.

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

Completeness5/5

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

For a destructive, refusal-prone mutation with no output schema, the description supplies the missing operational context: reversibility, ordering constraints, error codes, and the lifecycle reason for refusal. Nothing an agent needs to call this correctly is absent.

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 coverage is only 33%, and the description never mentions the 'force' parameter or its escape-hatch semantics, leaving that entirely to the schema. Required project/flag are self-evident, so the description neither compensates for nor worsens the coverage gap.

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

Purpose5/5

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

States a specific verb+resource ('Archive a flag') and immediately disambiguates it from delete_flag by parenthetically defining it as a 'soft-hide, evaluation stops serving it.' The relationship to restore_flag is named, so the agent can place it in the sibling set without reading a schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions and alternatives: archive dependents first, pointing to 'blockedBy in find_stale_flags / list_removal_candidates'. It also tells the agent when the tool will refuse and why, which is exactly the when/when-not guidance an agent needs before calling.

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

Deploy Server

Other Tools