Retrieve study results

---
name: retrieve-study-results
description: Use when the user wants to fetch an existing User Intuition study report, inspect its evidence coverage, or follow a finding or participant response to supporting interview evidence without regenerating analysis.
---

1. Use the supplied study ID. If only a name is supplied, resolve it with `list_studies` and disambiguate matches. Fetch `get_study` for audience and study context when needed.
2. Discover the current schema for `get_study_report`. Its default `view="overview"` is intentionally small; use `view="full"` or one of `study_findings`, `participant_profiles`, `participant_responses`, `evidence_coverage`, `recommended_next_steps`, or `references` when the task needs that section. Read `included_sections` before treating an absent section as empty. This is a read workflow: do not call `generate_report`, create a study, invite participants, or launch recruitment merely to fulfill retrieval.
3. Inspect the relevant Study Findings, Evidence Coverage, Participant Responses, Participant Profiles, Recommended Next Steps, and References sections. Learning Goals are answerable research questions with evidence requirements; legacy `key_questions` fields may carry their per-interview analysis. Preserve assessment status and whether requirements were specified before collection, revised, inferred, or of unknown timing. Profiles describe the actual sample rather than proving audience alignment.
4. Preserve study ID, report version or generation time, coverage, freshness, and source references when provided. Missing freshness is unknown, not fresh. Report-eligible interviews, completed interviews, and the target sample are different counts.
5. Resolve each reference using the returned reference map and identifiers. Keep respondent labels scoped to the study/report. Do not assume a response label is a participant ID or a reference ID is an interview ID. Follow interview references with `get_interview`; retain message or passage identifiers if present.
6. Before presenting an exact quotation or treating a finding as verified, inspect the original supporting passage. Do not invent finer citation precision than the response provides. Distinguish multiple quotes from one interview from independent participants.
7. Return supported conclusions, material limits, and their implications for the research purpose. Use the report's saved sample size and evidence assessment rather than recomputing study-level coverage from today's interviews. Missing per-interview analysis is an operational limitation. Trace recommendations through `gap_ids` to this report's `evidence_gaps`; a valid empty list is authoritative and differs from unavailable recommendations. Do not invent additional research or infer a need to recruit from small sample size alone. If new analysis is needed, explain that it is a separate operation and follow the user's scope.

The calling agent interprets the evidence in its wider context. The illustrative [results example](https://github.com/user-intuition/examples/tree/main/examples/retrieve-study-results) shows the intended B2 shape; verify it against the released schema before live use. [API reference](https://docs.userintuition.ai/api-reference/introduction).