Problem

Current loom uses a galaxy-mcp version that predates user-defined tools (UDTs). When a user asks the agent to create a UDT in a workflow, the agent falls back to its training data and produces old-school XML tool wrappers in a local directory -- not what the user asked for. User feedback:

it doesnt seem to always know galaxy lingo? like i asked if it could make user defined tools in a workflow for me, and it was like sure here you go and pointed me to a directory it had made locally of old school xml tools. i had to tell it what user defined tools were but id like it to just know what i was talking about.

Plan

• UDT support is built on the galaxy-mcp side; a new release is landing this week
• Once cut, bump the dependency in loom
• Verify UDT creation end-to-end against a real Galaxy (create UDT, reference from a workflow, invoke)
• Update any Galaxy-concept glossary / system prompt references so "user-defined tool" / "UDT" is recognized and reached for

Related watch-item (not filing separately yet)

Same failure mode -- brain falling back on training-era Galaxy terminology -- could recur for other newer concepts. Worth keeping an eye on; may deserve a dedicated glossary pass in the brain prompt later.