Flagbearer

List flags

list_flags

Read-only

List an application's feature flags with whether each is on, and its rollout percent, in every environment.

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": "list_flags"
  }
}

Input Schema

Name	Required	Description	Default
`applicationId`	Yes

Output Schema

Name	Required	Description	Default
`flags`	Yes
`environments`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint=true annotation already establishes the safe-read profile, and the description adds the useful scope fact that results span every environment and include rollout percentages. It says nothing about large result sets, pagination, or behavior for invalid application IDs, so it adds modest value over the annotation rather than rich behavioral context.

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?

One tightly packed sentence with no filler, and the verb plus resource lead off immediately. The trailing clauses about returned fields and environment scope are informative rather than redundant.

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 spelled out, and the tool is simple with a single required parameter. The description is nearly sufficient; only edge-case behavior such as pagination or missing applications is unaddressed.

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?

With 0% schema description coverage on the single applicationId parameter, the description must carry the meaning; "an application's feature flags" does tie the parameter to the target application. Beyond that link it adds no semantics, and the ID format is left to the schema's pattern.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List an application's feature flags") plus the fields returned (on/off state, rollout percent) and scope (every environment). It doesn't name a sibling such as get_user_flags to distinguish the application-wide view from the user-scoped one, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the mention of "an application's" signals that an applicationId is the entry point, and the read-only nature is evident. No when-to-use or when-not-to-use guidance appears, and no alternative is offered for per-user flag views or for listing applications first.

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.