Skip to main content
Glama
npow

metaflow-mcp-server

by npow

compare_cards

Compare Metaflow cards from multiple runs side by side. Generates an HTML page for visual comparison and text summaries for analysis.

Instructions

Compare Metaflow cards across multiple runs side by side.

Creates an HTML comparison page and returns it. Save the html field to a local .html file and open it in your browser to view the cards side by side. Also returns text summaries of each card for analysis.

Two ways to specify which cards to compare:

Option A -- provide a list of step/task pathspecs directly: pathspecs=["MyFlow/100/validate", "MyFlow/101/validate"]

Option B -- provide flow_name + step_name + run_ids (shorthand): flow_name="MyFlow", step_name="validate", run_ids=["100", "101"] Resolves each to "MyFlow/{run_id}/{step_name}" (first task).

Args: pathspecs: List of step or task pathspecs to compare. flow_name: Flow name (used with step_name + run_ids). step_name: Step name (used with flow_name + run_ids). run_ids: List of run IDs to compare (used with flow_name + step_name). card_type: Filter cards by type before selecting. card_id: Filter cards by ID before selecting. card_index: Which card to use if multiple match (default 0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathspecsNo
flow_nameNo
step_nameNo
run_idsNo
card_typeNo
card_idNo
card_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Describes that it creates an HTML page and returns it, and that text summaries are returned. Lacks details on side effects, prerequisites (cards must exist), or error handling, but sufficient given no annotations.

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?

Well-structured with bullet points and code examples. Slightly lengthy but all info is relevant. Front-loaded with main purpose.

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

Completeness4/5

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

Explains functionality, parameters, and return value adequately for a comparison tool. Lacks error cases or limitations, but overall complete given no annotations and good schema coverage via description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant meaning beyond schema: explains how run_ids resolve to pathspecs, default card_index, and filtering by type/id. Schema had no descriptions, so description compensates well.

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 the tool compares Metaflow cards across runs side by side, creates an HTML page, and returns text summaries. It distinguishes from siblings like get_card and diff_runs by focusing on comparison.

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

Usage Guidelines4/5

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

Provides two clear methods (pathspecs or flow+step+run_ids) with examples. Does not explicitly compare to siblings, but usage context is well explained.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/npow/metaflow-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server