FEAT: expose explicit data shape metadata in load_data_source - #417
biru-codeastromer wants to merge 1 commit into
Conversation
|
The idea (self-describing handles) still fits the current design and #416 is open. Two things are needed: (1) rebase onto main; there is one small conflict in executor.py where main now normalises the stored handle to a PeriodIndex (#531): keep that block and add your metadata call after it; (2) compute target_scitype / n_target_columns / target_variates instead of hardcoding 'Series', 1, 'univariate'; inspect_data already uses sktime.datatypes.check_is_scitype, so please reuse that so panel/multivariate handles are reported correctly. |
|
Had a look, Also |
Summary
Closes #416.
This adds explicit agent-friendly shape metadata to
load_data_sourceandload_data_source_asyncresponses so MCP clients can reason about loaded data handles without guessing from raw column names and dtypes.What changed
Executortarget_scitypetarget_variateshas_exogexog_variatesindex_typen_target_columnsn_exog_columnsWhy this matters
This makes loaded data self-describing for agents before they choose estimators or workflow branches. In particular, it reduces ambiguity around:
Validation
.venv/bin/ruff check src/sktime_mcp/runtime/executor.py tests/test_data_sources.py.venv/bin/ruff format --check src/sktime_mcp/runtime/executor.py tests/test_data_sources.py.venv/bin/pytest tests/test_data_sources.py -q.venv/bin/pytest -q