---
summary: "find_eligible condition re-rank; get_study_record referenceLimit; search_studies EnrollmentCount:desc guidance"
breaking: false
security: false
---

# 2.7.0 — 2026-06-11

## Added

- **`get_study_record` `referenceLimit`** input caps `referencesModule.references` to the given count, mirroring `locationLimit` / `outcomeLimit`. Pre-cap total is preserved in `filtersApplied.totalReferences`; `seeAlsoLinks` are never capped. The `## References` heading appends `(N of total)` when a cap is applied. ([#73](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/73))

## Changed

- **`find_eligible` condition re-rank** — results are stable-sorted so studies whose own condition list names a requested condition rank above tangential matches ClinicalTrials.gov's fuzzy `query.cond` Essie search pulls in via the MeSH umbrella. Recall is unchanged (nothing dropped, only reordered). A Von Willebrand bleeding-disorder trial that ranked #1 for an obesity/cardiovascular patient query no longer does. ([#72](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/72))
- **`find_eligible` `conditions` description** corrected — removed incorrect AND/OR/NOT and `,`-as-AND operator language; the handler always OR-joins entries (multi-word entries match as phrases). ([#72](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/72))
- **`search_studies` `sort` description** updated — `EnrollmentCount:desc` now includes guidance to pair with `AREA[StudyType]INTERVENTIONAL` for "largest trials" queries (observational registry/claims studies otherwise dominate), and notes enrollment counts are sponsor-reported and not range-validated. ([#74](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/74))

## Fixed

- **`find_eligible` off-condition trial ranking** — studies with no direct condition overlap with the patient's requested conditions no longer rank at the top of eligibility results due to upstream MeSH-umbrella fuzzy matching. ([#72](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/72))
