No user-submitted related servers found.
Scored across 24 tools
Each tool has a clearly distinct purpose, from run management (get_run, run_flow, resume_run) to artifact handling (get_artifact, list_artifacts, search_artifacts) to comparisons (diff_runs, compare_cards). There is no ambiguity between similar-sounding tools like get_recent_runs and search_runs, as their descriptions clarify different scopes and filters.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_run_tags, get_config, list_flows). Even compound names like get_latest_failure or get_triggered_run_status adhere to the pattern. No mixing of conventions (camelCase or other styles) is present.
With 24 tools, the set is slightly above the typical well-scoped range (3-15) but remains justified for the Metaflow domain, which involves many distinct operations (runs, artifacts, cards, deployments, tags, etc.). The count is not excessive given the platform's complexity.
The tool surface covers most core workflows: running flows (locally and triggered), monitoring, fetching artifacts and logs, comparing runs, managing tags, and viewing cards and deployments. Minor gaps exist, such as no explicit tool to abort a locally run flow (only triggered runs) and no tool to delete runs or artifacts, but these do not severely hinder typical agent tasks.
