Skip to main content
Glama
Sign In
Featureflip

Featureflip

Official
by canopy-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List flag triggers

list_flag_triggers
Read-only

List a flag's triggers in one environment, or get one by passing trigger: id, name, action (Enable or Disable), whether each is enabled, the last four characters of its secret, and when it last fired.

Instructions

List a flag's triggers in one environment, or get one by passing trigger: id, name, action (Enable or Disable), whether each is enabled, the last four characters of its secret, and when it last fired. A trigger is a secret URL that a monitoring tool (a Grafana alert, a Datadog monitor) calls to turn the flag on or off. The URL is never listed; it is shown once, when manage_flag_trigger creates or rotates it.

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_flag_triggers"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds security-relevant behavior beyond that: the secret URL is never returned by this tool and secrets are shown only as the last four characters. That is exactly the kind of non-obvious constraint an agent needs to avoid promising a user a URL from a list call.

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?

The operation and single-item mode are front-loaded in the first clause, followed by supporting context. Slightly dense, the returned-fields enumeration and trigger definition sit inside one long sentence, but nothing is padding.

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?

An output schema exists, so the tool is not obligated to describe returns, yet the description covers the relevant shape anyway plus the critical caveat about URL non-disclosure. Combined with full schema coverage and a readOnly annotation, an agent has everything needed to call this correctly.

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 100%, so all six parameters including trigger, cursor, and limit are already documented in structured data. The description adds meaning for the trigger parameter (single fetch instead of listing) but nothing about pagination or environment scoping beyond what the schema states, so it lands at baseline rather than above it.

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 first sentence names a specific verb and resource ('List a flag's triggers in one environment') and explicitly states the single-item variant when a trigger id is passed. It also defines what a trigger actually is, so an agent can tell it apart from manage_flag_trigger without opening 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 Guidelines4/5

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

It clearly indicates the read path ('list ... or get one by passing trigger') and implicitly contrasts with manage_flag_trigger, which creates or rotates triggers, by noting the URL is only shown at creation. It stops short of an explicit 'use this when you need to audit triggers' statement, but the guidance is inferable and sufficient.

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