Skip to main content
Glama

train_baseline

Train a baseline classification or regression model on a local CSV dataset and report evaluation metrics, giving a reference point for model comparison.

Instructions

Train one baseline model and report evaluation metrics.

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>",
      "model_name": "<model_name>"
    },
    "name": "train_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDataset filename.
stratifyNoStratify split (classification only, default true).
task_typeYes'classification' or 'regression'.
test_sizeNoTest fraction (default 0.2).
model_nameYesModel to train.
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?

No annotations are provided, so the description carries the full behavioral burden. It says training and metric reporting occur, but does not disclose whether a model artifact is saved, what metrics are returned, whether the operation is expensive, or what side effects occur.

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 a single front-loaded sentence with no wasted wording. It communicates the core action and outcome efficiently.

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 a seven-parameter training tool with no annotations and no output schema, the description is too thin. It does not explain return values, model persistence, or how the tool relates to predict, export_model, or compare_models.

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 all seven parameters are already documented in the input schema. The description adds no additional parameter meaning, which is acceptable given the schema's completeness but does not exceed the baseline.

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?

The description states a specific verb and resource: 'Train one baseline model and report evaluation metrics.' The word 'one' helps distinguish it from compare_models, but it does not explicitly name or contrast with any sibling tool.

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 guidance on when to use this tool versus alternatives such as compare_models or predict, nor are prerequisites or typical workflow context provided. The baseline framing implies usage but does not state it explicitly.

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