Skip to main content
Glama
Axiomatic-AI

axiomatic-mcp

Official
by Axiomatic-AI

AxModelFitter_calculate_information_criteria

Calculate AIC, BIC, and AICc to compare model architectures and avoid overfitting. Provide MSE or MAE loss, parameter count, and noise sigma for Gaussian or Laplace likelihood.

Instructions

Calculate AIC and BIC information criteria for model selection.

REQUIRED INPUTS:
- loss_value: MSE or MAE value from your optimization
- cost_function_type: Either 'mse' or 'mae' only
- n_parameters: Number of fitted parameters in your model
- sigma: Noise standard deviation (REQUIRED for MSE, None for MAE)
- data_file: Path to your data file
- output_data: Which columns contain your output data

WHEN TO USE:
- Compare different model architectures (linear vs exponential vs polynomial)
- Select best model complexity (avoid overfitting)
- Use AIC/BIC values: lower is better

SIGMA PARAMETER:
- For MSE (Gaussian noise): Provide noise std dev from domain knowledge
- For MAE (Laplace noise): Set sigma to None
- Example: experimental measurement error ±0.1 volts → sigma=0.1

RETURNS: AIC, BIC, AICc values with interpretable model comparison metrics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
n_obsNoExplicit count of independent residuals. If None, infers from output data
sigmaYesREQUIRED noise std dev for diagonal covariance Σ=σ²I. Specify from domain knowledge or estimate based on available data.
data_fileYesPath to data file (CSV, Excel, JSON, Parquet). All data must be provided via file.
loss_valueYesMean loss value from optimization (MSE or MAE only)
file_formatNoFile format: 'csv', 'excel', 'json', 'parquet' (auto-detect if None)
output_dataYesOutput column mapping: {'columns': ['y'], 'name': 'y', 'unit': 'volt'} or {'columns': ['y1', 'y2'], 'name': 'y', 'unit': 'volt'}
df_effectiveNoEffective degrees of freedom for penalized models (EXCLUDING scale)
n_parametersYesNumber of fitted parameters in mean function (scale param added automatically)
n_scale_paramsNoNumber of scale parameters: 1 for single-output, d for d-output with separate scales
aicc_include_scaleNoInclude scale parameter in AICc correction (literature varies)
cost_function_typeYesLoss function type: 'mse' (Gaussian) or 'mae' (Laplace) only
include_scale_paramNoInclude scale parameter (σ² or b) in k count
Behavior4/5

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

No annotations provided, so description covers behavior: calculates AIC, BIC, AICc, requires specific parameters, and explains sigma parameter usage with example. Lacks disclosure of error handling or return format details.

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?

Well-structured with sections for required inputs, when to use, sigma parameter, and returns. Each sentence serves a purpose, no redundancy, efficient use of text.

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?

Covers core functionality and key parameters but could elaborate on return interpretation beyond 'lower is better' and handling of optional parameters like n_scale_params and aicc_include_scale. Adequate but not exhaustive.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant value by explaining sigma requirement in detail, providing examples, and clarifying n_obs inference. Goes well beyond schema descriptions.

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 it calculates AIC and BIC for model selection, with specific verb 'calculate' and resource 'information criteria'. It distinguishes from siblings like cross_validate_model and compare_models by focusing on information criteria.

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?

Includes a 'WHEN TO USE' section guiding comparison of model architectures and complexity selection. Does not explicitly state when not to use or name alternatives, but provides clear context for appropriate usage.

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/Axiomatic-AI/ax-mcp'

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