Skip to content

docs(mcp): clarify feature flag discovery vs canonical UI navigation#59

Open
alohaninja wants to merge 3 commits intomainfrom
feature/feature-flags-doc-guidance
Open

docs(mcp): clarify feature flag discovery vs canonical UI navigation#59
alohaninja wants to merge 3 commits intomainfrom
feature/feature-flags-doc-guidance

Conversation

@alohaninja
Copy link

@alohaninja alohaninja commented Mar 24, 2026

Summary

  • Clarifies that list-feature-flags is for discovery and should not be used to construct UI links.
  • Documents the canonical navigation flow: call get-feature-flag and use environments.<environmentKey>.site.href.
  • Adds explicit filter guidance (query:<text>, tags, state, hasExperiment, maintainerId, hasDataExport) to improve agent query quality.
image

Test plan

  • Reviewed tool descriptions for correctness and consistency.
  • Confirmed no runtime/tool registration behavior changes.

Made with Cursor


Open with Devin

Clarifies that list-feature-flags is discovery-only and that get-feature-flag environment site links should be used for UI navigation.

Made-with: Cursor
@alohaninja alohaninja requested a review from nieblara March 24, 2026 18:55
devin-ai-integration[bot]

This comment was marked as resolved.

alohaninja and others added 2 commits March 25, 2026 13:47
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant