Skip to main content
Glama
kkruglik

MLflow MCP Server

by kkruglik

query_runs

Read-only

Filter and sort MLflow runs using MLflow's filter syntax, with pagination support for large result sets.

Instructions

Query runs using MLflow's filter syntax with optional sorting.

Runs can be large. Use wise limits to avoid flooding context.

Args: experiment_id: The experiment ID query: MLflow filter string (e.g., 'metrics.accuracy > 0.9') limit: Maximum number of runs to return offset: Number of runs to skip order_by: List of sort clauses, e.g. ['metrics.rmse DESC', 'params.lr ASC']. Use backticks for special characters: ['metrics.trading/loss DESC']

Examples: query_runs("1", "metrics.accuracy > 0", order_by=["metrics.accuracy DESC"]) query_runs("1", "", order_by=["metrics.f1/score DESC"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
experiment_idYes
queryYes
limitNo
offsetNo
order_byNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The annotations already set readOnlyHint=true, and the description adds valuable context about potential large result sizes and the need for limits. No contradiction between description and annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concisely structured with sections for args, examples, and a warning. Every sentence adds value, and it is well organized for an AI agent.

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

Completeness5/5

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

Given the tool's complexity (5 params, output schema present), the description covers all parameters with examples and syntax details. The output schema is available, so return value description is not needed.

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?

With 0% schema coverage, the description compensates by explaining each parameter, including the MLflow filter syntax and the backtick handling for order_by. It provides examples that add meaning.

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?

The description explicitly states it queries runs using MLflow's filter syntax with optional sorting. It distinguishes from siblings like 'search_runs_by_tags' and 'get_runs' by highlighting the MLflow filter syntax, a specific verb and resource.

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?

The description warns that 'Runs can be large. Use wise limits to avoid flooding context,' providing implicit guidance on when to use and caution. It does not explicitly state when not to use, but the context is clear.

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/kkruglik/mlflow-mcp'

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