From 66530a074f2de87ca4e3f1df2c4f528e1827a278 Mon Sep 17 00:00:00 2001 From: Maurice Date: Fri, 28 Aug 2026 13:45:31 +0200 Subject: [PATCH] feat(mcp): register the new surfaces, and point the model at the units Ten new controllers in the test registry, and one line in the session instructions: without it nothing tells an assistant to read the display settings before rendering a temperature, which is what makes that tool worth having. --- server/src/nest/mcp-transport/mcp-transport.constants.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/server/src/nest/mcp-transport/mcp-transport.constants.ts b/server/src/nest/mcp-transport/mcp-transport.constants.ts index bec0641b5..a0396c0cd 100644 --- a/server/src/nest/mcp-transport/mcp-transport.constants.ts +++ b/server/src/nest/mcp-transport/mcp-transport.constants.ts @@ -69,6 +69,7 @@ The following features are optional and may not be available on every TREK insta - When the user asks to "add X to day Y", resolve both the place (search + create if needed) and the day ID before calling \`assign_place_to_day\`. - Do not batch destructive operations (delete trip, delete day, delete place) without explicit user confirmation for each. - Present budget amounts with the trip's currency. Use \`get_trip_summary\` to read the currency field. +- Read \`get_display_settings\` before rendering a temperature, a distance or a clock time: the user has picked units, a time format and a default currency, and guessing at them contradicts what they see in the app. - For group trips, always check member IDs via \`list_trip_members\` before calling tools that require a \`userId\` (e.g. budget splits, assignment participants). `.trim();