Skip to main content
Glama
Sign In

The Bridge

by dev.thebridge
OverviewDiscussionsAdmin

Set Feature Flag Schedule

set_flag_schedule
Idempotent

Schedule a future state transition on a feature flag, by KEY. The flag keeps its current state until the timestamp, then moves to the scheduled state. Arguments: key, at (an ISO-8601 timestamp such as 2026-09-01T09:00:00Z), and state (off | on | on-with-rule). Setting a schedule replaces any existing one; use clear_flag_schedule to remove it. This writes the scheduled transition onto the flag — it does not change the current state, so the flag behaves exactly as before until the timer fires. Fails with FLAG_NOT_FOUND when no flag has the given key. Before writing app code that consumes this, call get_integration_guide with topic=feature-flags and the framework the app uses.

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": {
      "key": "<key>",
      "at": "<at>",
      "state": "<state>"
    },
    "name": "set_flag_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesISO-8601 timestamp at which the transition fires, e.g. "2026-09-01T09:00:00Z".
appNoId of the Bridge app to act on for this call (see list_apps). Omit to use the current app.
keyYesFlag KEY to schedule (see list_feature_flags).
stateYesState the flag moves to when the timer fires.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare non-read-only, idempotent, non-destructive, closed-world, but the description adds genuinely new behavior: the write does not alter the flag's current state until the timer fires, that setting a schedule overwrites any existing schedule (a side effect the destructiveHint=false hint does not convey), and the FLAG_NOT_FOUND failure mode. This is meaningful disclosure beyond the structured fields.

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?

Front-loaded with the core action and the semantics that follow, and most sentences carry non-obvious information. The 'Arguments:' sentence largely duplicates the schema and the get_integration_guide pointer is slightly tangential, so it is efficient but not maximally tight.

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 4-parameter mutation tool with no output schema, the description covers effect on current state, replacement semantics, error behavior, and an integration prerequisite — everything an agent needs to call it correctly without follow-up. Return-value detail is unnecessary since no output schema exists.

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 schema already documents key, at, state and app. The description restates key/at/state and the enum values, adding only the 'by KEY' emphasis and format example already present in the schema, and it omits the optional app parameter entirely. Baseline 3 is appropriate when the schema carries the parameter detail.

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 (schedule), a specific resource (a future state transition on a feature flag) and the exact scope ('keeps its current state until the timestamp, then moves to the scheduled state'). It is immediately distinguishable from siblings like clear_flag_schedule, toggle_feature_flag and update_feature_flag without opening any 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?

Explicitly names the alternative for the inverse operation ('use clear_flag_schedule to remove it'), warns that a new schedule replaces an existing one, and prescribes a prerequisite ('call get_integration_guide with topic=feature-flags'). When-to-use, when-to-be-cautious, and the adjacent tool are all covered.

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

All The Bridge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources