Skip to content

re-organize the 'Feature Group' labels #189

Closed
@devoncarew

Description

@devoncarew

We may want to re-organize the 'Feature Group' labels for the MCP tools, from here:

https://github.com/dart-lang/ai/tree/main/pkgs/dart_mcp_server#tools

  • we're not consistent w/ multi-word labels (static analysis, static_analysis, runtime analysis)
  • I don't know that there's any emerging pattern wrt feature group labels, but from the firebase MCP page, I see all their group labels use single words (https://firebase.google.com/docs/cli/mcp-server#capabilities)
  • I myself don't know how relevent the feature group label is to the LLMs consuming the tools

I would likely propose that we standardize on analysis, project, packages, runtime, editor, and configuration.

We may also want to do some cleanup / normalization on the tool names themselves; I don't know what would best help either categorize them, or, make them more consumable to LLMs.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions