Skip to main content
Glama

auto_modeling_audit

Evaluate if your data is ready for modeling: detects leakage, multicollinearity, instability, temporal issues, and class imbalance, then provides a verdict and mitigation steps.

Instructions

'Can I train a model on this without footguns?'

    Chains leakage + multicollinearity + stability + temporal* + class imbalance
    into a single ranked-blocker brief with a verdict (do_not_train_yet /
    train_with_mitigations / ready_to_train).

    Downsamples to `max_rows` via reservoir sampling when the source is
    larger — the per-column correlations these checks run can time out on
    7M+ row sources but converge to the same conclusions at ~500K rows.
    Set `max_rows` higher (or to a number above the source size) for the
    full pass. The sample is materialized once and surfaced in `sample_info`.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_rowsNo
source_idYes
time_columnNo
target_columnYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It reveals downsampling via reservoir sampling, performance caveats on 7M+ rows, convergence at ~500K rows, and that the sample is surfaced in sample_info. This is substantial added context.

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 compact yet rich: a hook, a clear core statement, and two sentences of behavioral guidance. Every sentence earns its place with no fluff.

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?

The description covers purpose, verdicts, sampling behavior, and output field, and an output schema exists. It is complete for the tool's complexity, with no critical gaps.

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?

Schema description coverage is 0%, so description must compensate. It provides detailed guidance on max_rows, explaining its role in downsampling and how to adjust for a full pass. Other parameters are self-explanatory or hinted (time_column for temporal), making this adequate.

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 clearly states the tool's function: assessing model-readiness by chaining multiple checks into a ranked-blocker brief with a verdict. It uses a specific verb ('Chains') and names exact checks, distinguishing it from sibling check_* tools.

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 opening question 'Can I train a model on this without footguns?' provides clear context for when to use the tool. It implies it is the holistic model-readiness audit, but does not explicitly mention alternatives or exclusions, so it earns a 4 rather than 5.

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/charliecpeterson/edamcp'

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