Summary
MATLAB becomes something an agent can call, with the script that produced a result kept when you want it.
Two tools cover the whole loop — describe, generate, run, read the output — and the saveScript and scriptPath pair is what makes it more than a scratchpad, since the code behind a number survives the conversation. What is not here is everything around a session: no workspace inspection, no variable listing, no figure or plot handling, so anything past running code and reading its output sits outside this set.
What it is
A two-tool bridge to a MATLAB installation: one executes code and returns the results, the other generates code from a natural language description.
What you get
- execute_matlab_code runs MATLAB code and returns the results into the conversation
- generate_matlab_code turns a description of what you want into MATLAB code, which execute_matlab_code can then run
- saveScript and scriptPath on both tools, so the code behind a result is left on disk instead of living only in the transcript
Requirements
A MATLAB installation the server can drive, and a writable scriptPath when saveScript is set. Apache-2.0 licensed.