Skip to main content
Glama
Sign In
@loggydev/mcp-server

@loggydev/mcp-server

by loggy-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

toggle_feature_flag

Enable or disable a feature flag to control feature rollout, with optional percentage-based targeting for gradual releases.

Instructions

Enable or disable a feature flag

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": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "toggle_feature_flag"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFeature flag ID
enabledYesWhether to enable or disable the flag
percentageNoOptional: set rollout percentage (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided. Description only states the basic operation, omitting behavioral details such as whether the change affects all environments, if it's instantaneous, or any side effects like toggling during an active rollout.

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?

Extremely concise at one sentence. No wasted words, but could benefit from slightly more context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing context such as return value, error conditions, and whether the flag must exist prior to toggling. For a mutation tool with no output schema, this leaves significant gaps for the agent.

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 covers 100% of parameters with descriptions. The description does not add extra meaning beyond the schema. Baseline 3 is appropriate because schema already documents parameters adequately.

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?

Description clearly states verb and resource: 'Enable or disable a feature flag'. Distinguishes from sibling tools like create_feature_flag (creates new flag) and list_feature_flags (lists existing).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Does not mention prerequisites (flag must exist), rollout strategies, or relationship to other tools like create_feature_flag.

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