Skip to main content
Glama

Feature flag debt audit

submit_feature_flag_audit
Idempotent

Find feature flags that are declared but appear nowhere in the source, and deliver a removal plan. During flag cleanup, when you have the flag list and the source. Do not choose this when flags are resolved dynamically, which a textual check cannot follow. Example requests: Which feature flags can I delete? | Find dead feature flags in this source tree. | Audit my flags and tell me what is safe to remove.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_feature_flag_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behaviour, so the safety profile is covered. The description adds genuine value with the dynamic-resolution limitation and by stating the output is a removal plan. However, it never mentions that this is a priced job requiring a quote_id and authorized_by — the schema carries that, but the workflow implication (quote, authorize, then pay) is the biggest behavioural omission here.

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 purpose, then prerequisites, then exclusions, then examples — a sound ordering with no filler in the first two sentences. The three example requests are mildly redundant with the opening line but aid intent matching, so the cost is small.

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

Completeness3/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 explained, and the 1 MB text-input constraints live in the schema. What is missing is job-shape context: that this is one of many submit_* priced capabilities gated by a quote and an authorizer, and how it relates to siblings like preflight_job or select_capability. Adequate for a simple two-input tool, but not complete for an agent navigating a priced job pipeline.

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 75%, so the schema already explains flags, source, quote_id, accepted_price and authorized_by. The description adds only the loose framing "you have the flag list and the source" and nothing about the pricing or authorization parameters. Baseline 3 is correct when the schema does the heavy lifting.

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?

"Find feature flags that are declared but appear nowhere in the source, and deliver a removal plan" names a precise verb (find) plus the artifact produced (removal plan), which cleanly separates it from neighbours like submit_json_key_audit or submit_json_diff. The agent knows the exact analysis without opening the 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?

"During flag cleanup, when you have the flag list and the source" states the prerequisites and the moment to use it, and "Do not choose this when flags are resolved dynamically, which a textual check cannot follow" gives an explicit exclusion with a reason. The example requests reinforce routing for an agent matching user intent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources