Skip to main content
Glama
Featureflip

Featureflip

Official

List change freezes

list_change_freezes
Read-only

List change freeze windows or retrieve one by ID to see which environments block flag changes, when freezes end, and how scheduled changes are handled by policy; filter by status or project.

Instructions

List change freeze windows, or get one by passing freeze_id. A freeze blocks flag changes in the environments it covers (toggles, targeting, ramps, copies) until it ends; scheduled changes due inside it are held or failed per its policy. Filter by status (Upcoming, Active, Ended) and project. Each window shows its environments, end time, scheduledChangePolicy and the approvals that let scheduled changes through. A single get also returns an etag for manage_change_freeze action=update. Listing and getting work on any plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_change_freezes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 20)
cursorNonext_cursor from a previous response
statusNoOnly windows in this state
projectNoOnly windows for this project key (project windows)
freeze_idNoFreeze id: get just that window instead of listing

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.11.1

TDQS

A4.5/5.0
Behavior5/5

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

With annotations only declaring readOnlyHint, the description adds substantial behavioral context: a freeze blocks flag changes across environments, holds or fails scheduled changes per policy, and returns environments, end time, scheduledChangePolicy, and approvals. It also notes the etag behavior for a single get and plan availability.

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 dense but well organized: purpose and get-one mode first, freeze semantics second, filters and returned fields next, then the etag and plan note. Every sentence carries useful information without repetition.

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?

The tool has an output schema and full schema coverage, and the description still supplies the operational context an agent needs: what a freeze does, how scheduled changes are affected, what filters exist, and how the single-get etag relates to the management tool. Nothing important for correct invocation 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%, so all five parameters are already documented in the schema, including the status enum and freeze_id behavior. The description restates their meaning but adds little syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The description opens with a specific verb and resource: list change freeze windows, with an explicit single-item mode via freeze_id. It clearly distinguishes this read operation from the mutation path by pointing to manage_change_freeze action=update.

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

Usage Guidelines4/5

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

It explains the main usage modes: list windows, get one by freeze_id, and filter by status or project. It also identifies manage_change_freeze action=update as the consumer of the single-get etag, though it does not spell out explicit when-not-to-use conditions.

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