Declare Study Holdout Use
declare_study_holdout_useRecord how study holdout results were used by submitting an evidence-use declaration with disposition and reason, referencing a prior access event. Ensures revision influence is validated and traceable.
Instructions
Append a submitter-reported evidence-use declaration using project-owner credentials and create:models. Read get_study_prediction_access first and reference an access event from this run. Use a fresh UUID declaration_id and reuse it unchanged on retry. informed_revision requires a published affected revision in the same study; other dispositions omit it. Reason must explain actual use. Reported revision influence requires fresh validation for affected revisions; later review-only notes cannot erase it. Does not certify independence, accept or promote a model. API submissions remain identified as reported declarations.
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": {
"run_id": "<run_id>",
"declaration_id": "<declaration_id>",
"source_access_id": "<source_access_id>",
"disposition": "<disposition>",
"reason": "<reason>"
},
"name": "declare_study_holdout_use"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | ||
| run_id | Yes | ||
| disposition | Yes | ||
| declaration_id | Yes | ||
| source_access_id | Yes | ||
| affected_revision_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||