Skip to main content
Glama
Featureflip

Featureflip

Official

List rollout ramps

list_rollout_ramps
Read-only

List a flag's rollout ramps in an environment, or fetch one ramp with its etag to manage its timed percentage rollout.

Instructions

List a flag's rollout ramps in one environment (the active ones, newest first, then the ten most recently finished), or get one by passing ramp. A ramp raises a percentage rollout one step at a time on a timer. Each ramp shows its status (Running, Paused, Completed, Aborted), its steps, currentStepIndex, nextStepAt, and why it paused. A single ramp comes with an etag to pass as ifMatch to manage_rollout_ramp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "flag": "<flag>",
      "environment": "<environment>"
    },
    "name": "list_rollout_ramps"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagYesFlag key or id
rampNoRamp id: get just that ramp (with its etag) instead of listing
limitNoPage size (default 20)
cursorNonext_cursor from a previous response
projectYesProject key
environmentYesEnvironment key, e.g. production

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.1
    • changedOutput schema / $defs / PublicRampStep / description
      Previous value: -"One rung of a rollout ramp: the percentage served, then how long it holds before the next rung."New value: +"One rung of a rollout ramp: the percentage served, then how long it holds before the next rung. Both fields\nare required."
  2. Addedv0.10.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries the rest and does so well: it discloses the listing window (active ramps newest-first, then only the ten most recently finished), the per-ramp fields returned, and the etag needed downstream. It doesn't cover pagination semantics or behavior of limit/cursor, which the schema only gestures at.

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?

Four compact sentences, scoping and retrieval mode front-loaded, then the domain definition, then return shape and downstream etag usage. No filler or restated title.

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?

An output schema exists and annotations cover safety, so the remaining burden was scope, return content, and the etag handoff — all covered. Only pagination/limit interaction with the fixed 'ten most recently finished' window is left implicit.

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 the baseline is 3. The description reinforces ramp's dual role and the etag return, but adds nothing for limit or cursor beyond what the schema already says.

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 and resource ('List a flag's rollout ramps in one environment') plus the alternate single-item mode via the ramp parameter. It also defines what a ramp is ('raises a percentage rollout one step at a time on a timer'), which distinguishes it from flag/trigger siblings.

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?

Explicitly tells the agent how to switch from listing to single-fetch ('get one by passing ramp') and routes post-fetch management to manage_rollout_ramp via the etag/ifMatch handshake. No explicit when-not-to-use case, so it falls short of a 5.

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