---
summary: "Auto-normalize case/whitespace field-name mistakes (#44), surface Essie query parse errors with recovery hints (#34, #39), add locationLimit/outcomeLimit/nearLocation render controls on get_study_record (#40), and lift topAnalysis (p-value, CI, method) into get_study_results summary mode (#42)."
breaking: false
security: false
---

# 2.4.9 — 2026-05-20

Feature release closing five open issues. Three improvements harden the LLM-facing surface against common mistakes (silent field-name normalization, structured recovery hints on Essie parser failures, reserved-character documentation on every free-text query parameter), and two extend rendered output with caller-controlled knobs and statistical analysis lifting.

## Added

- **`clinicaltrials_get_study_record` render controls** ([#40](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/40)) — three new inputs replace hardcoded truncation ceilings. `locationLimit` (default 10, max 500, 0 = unlimited) and `outcomeLimit` (default 5, max 100, 0 = unlimited) cap the formatted text without affecting `structuredContent`. `nearLocation { lat, lon, radiusMi }` filters and sorts locations by Haversine distance from a point, annotates each line with miles, and notes the count of upstream sites missing coordinates. Primary outcomes still always render in full. `StudyLocation.geoPoint` added to the type.
- **`clinicaltrials_get_study_results` summary mode lifts `topAnalysis`** ([#42](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/42)) — first analysis (typically the primary one) per outcome measure surfaces in the structured `topAnalysis` field with `statisticalMethod`, `pValue`, `pValueComment`, `paramType`/`Value`, `ciPctValue`/`NumSides`/`Lower`/`Upper`, `nonInferiorityType`, `estimateComment`, and `groupIds` (present fields only). Renders as a single `Analysis:` bullet in formatted output. Closes the gap where summary mode condensed ~200KB → ~5KB but stripped the statistical significance signal researchers triage on.
- **`query_parse_error` reason on `clinicaltrials_search_studies` and `clinicaltrials_get_study_count`** ([#34](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/34)) — upstream `Error parsing query in <where>: no viable alternative …` failures now surface with the new typed contract entry and a recovery hint explaining that free-text fields take plain words plus AND/OR/NOT, with `[ ] ( ) ,` reserved by the Essie parser.
- **`sponsorQuery` on `clinicaltrials_get_study_count`** — parity with `clinicaltrials_search_studies` so a sponsor-scoped count no longer requires an `advancedFilter` workaround.

## Changed

- **Field-name validation auto-normalizes case-only and whitespace mistakes** ([#44](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/44)) — `ClinicalTrialsService.normalizeFields` runs before `validateFields` in `searchStudies` and `getFieldValues`. Unambiguous case-folded matches (`nctid` → `NCTId`, `BRIEFTITLE` → `BriefTitle`) and trimmed-whitespace matches pass through silently with `ctx.log.notice` for operator visibility, skipping the validation throw and the LLM tool-call round-trip. Truly invalid names still throw with the existing did-you-mean error. Case-fold map skips lowercase forms that collide across canonicals so the mapping stays ambiguity-free.
- **AREA[] field-name errors land on `field_invalid` reason with recovery hint** ([#39](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/39)) — upstream `Error parsing query in advanced filter: Unknown area name: \`X\`` now wraps with the offending field name and a pointer to `clinicaltrials_get_field_definitions`, matching the structured-recovery shape already used for the `fields` parameter.
- **Free-text query parameter descriptions document reserved characters** ([#34](https://github.com/cyanheads/clinicaltrialsgov-mcp-server/issues/34)) — every `query`/`conditionQuery`/`interventionQuery`/`locationQuery`/`sponsorQuery`/`titleQuery`/`outcomeQuery` parameter on `clinicaltrials_search_studies` and `clinicaltrials_get_study_count`, plus `conditions[]` on `clinicaltrials_find_eligible`, now warns inline that `[ ] ( ) ,` are reserved by the upstream parser. AREA[] guidance on the existing `field_invalid` contract entry extended to cover advanced-filter expressions.
- **`@cloudflare/workers-types` ^4.20260516.1 → ^4.20260521.1**, **`@types/node` ^25.8.0 → ^25.9.1**, **`@vitest/coverage-istanbul` ^4.1.6 → ^4.1.7**, **`vitest` ^4.1.6 → ^4.1.7** (devDeps).
