Flagbearer

Create a flag

create_flag

Create a feature flag in an application. It starts off in every environment; use set_flag to turn it on. The key is what code checks, like new-checkout.

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": {
      "applicationId": "<applicationId>",
      "name": "<name>",
      "key": "<key>",
      "description": "<description>"
    },
    "name": "create_flag"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`name`	Yes
`description`	Yes
`applicationId`	Yes

Output Schema

Name	Required	Description	Default
`flag`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add real value by stating the created flag 'starts off in every environment' and is inactive until set_flag is called — that initial-state behavior is not derivable from the schema. It omits what permissions are required, what happens on duplicate key, and whether the flag targets all environments by default in a way that is hard to undo.

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?

Three short sentences with no filler; the creation verb and initial-state caveat are front-loaded, followed by the sibling redirect and a concrete key example. Every sentence adds information an agent would otherwise have to guess.

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, so return values need not be described, and the description covers the creation semantics and next-step behavior well. The remaining gap is the required applicationId, whose source (presumably list_applications) is never indicated, which matters for a four-required-parameter mutation tool with zero annotation coverage.

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 0%, so the description must compensate for all four required parameters. It meaningfully explains key semantics ('what code checks, like new-checkout'), which clarifies the naming intent behind the regex pattern, but says nothing about applicationId, name, or description (e.g. whether description accepts null).

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 ('Create a feature flag in an application') and disambiguates from the nearest sibling by naming set_flag as the tool that turns flags on. An agent can tell this apart from set_flag and list_flags 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 Guidelines4/5

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

Explicitly routes the follow-up action to set_flag ('use set_flag to turn it on'), which tells the agent what this tool does NOT do. There is no explicit when-not-to-use condition or prerequisite call (e.g. list_applications for the applicationId), so it stops 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.

All Flagbearer tools Inspect

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.