pdac_subtype_agent_prod__run_findings_test_inputs – 1 MCP server offers this tool
What it usually takes
columns– in 1 of 1dataset_id– in 1 of 1sample_selection– in 1 of 1sets– in 1 of 1stratify_by– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
PDAC Subtype Agent co.huggingface.anne-voigt/pdac-subtype-agent-prod The exact inputs behind a ranking, packed for DecoupleRpy's significance test. ADR-0028 §7, second amendment. ``rank_findings`` says which associations are strongest; whether they hold up is DecoupleRpy's question (ADR-0027). Its ``compare_scores_by_group`` endpoint (DecoupleRpy ADR-0035) tests a score matrix someone else computed, and this door hands it the one this ranking read: the same scoring call, the same samples, the labels each two-group row compared, and each row's Cliff's δ so DecoupleRpy can prove the numbers match before it reports a p-value. The orchestrator forwards ``request`` unchanged. Same arguments as ``rank_findings`` and the same scoring path (:func:`_ranked_findings`), so the two cannot describe different numbers. This endpoint computes no test statistic: it packs numbers for another agent to test. Registered datasets only; an upload's matrix is never kept (ADR-0006 §4). ``sample_selection`` and ``columns`` are ``rank_findings``' trailing arguments and must be fo | columns,dataset_id,sample_selection,sets,stratify_by | Not stated |