Skip to main content
Glama

compare_models

Train and compare multiple classification or regression models on a dataset, then select a model using your chosen evaluation metric.

Instructions

Train and compare multiple models; select best by metric.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "target_column": "<target_column>",
      "task_type": "<task_type>"
    },
    "name": "compare_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvNoCross-validation folds (default 5).
nameYesDataset filename.
metricNoSelection metric (default auto).
modelsNoModels to compare.
task_typeYes'classification' or 'regression'.
test_sizeNoTest fraction (default 0.2).
random_stateNoRandom seed (default 42).
target_columnYesTarget variable column.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It does not disclose that this is a long-running, compute-heavy training operation, whether trained models are persisted or exported (a sibling, export_model, exists), whether existing models are overwritten, or what the result contains beyond "best by metric."

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?

A single front-loaded sentence with zero filler. Its brevity reflects under-specification rather than wasted wording, so it is efficient but thin.

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

Completeness2/5

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

For an 8-parameter training tool with no annotations and no output schema, the description omits what comes back (best model object, comparison table, scores), whether artifacts persist, and roughly what resources the run consumes. An agent could invoke it, but not predict or explain its results.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (cv, test_size, random_state, metric, models, task_type, etc.) is already documented in the schema; the baseline is 3. The description's "select best by metric" loosely ties to the metric parameter but adds no format, default, or interaction detail beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Train and compare multiple models; select best by metric" gives a specific verb (train/compare) and resource (models) plus the selection outcome. It implicitly distinguishes itself from single-model siblings like train_baseline, though it never names one, so the contrast is left to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: nothing says when to pick this over train_baseline, when comparison is inappropriate, or what prerequisites (prepared dataset, column types) must hold. A user must infer usage from the phrase "compare multiple models."

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