Repository navigation
One catalogue of operations for the library, the terminal and the MCP #1684
Description
Part of #746: v8.0's tool interface, and v9.0's terminal. From #1649.
Simplify, Expand, Factorize, Differentiate, Integrate and Limit on Entity are already adapters over the transformation catalogue in Core/Transformations/Transformation.Catalogue.cs. Nothing else the terminal or the MCP offers is in it, and the three surfaces are kept in step by hand.
Proposal: one catalogue with two kinds of entry.
- Transformations, as now:
Entity → Entity, each carrying its claim (EquivalenceorDerivation). - Queries:
Entity →a set, a number, text or a table. Solving, evaluation, LaTeX, a series and a truth table are queries.
Each entry carries its name, its arguments and a one-line description.
- The
Entitymethods stay the C# API, as thin adapters over the catalogue. amcli's one-shot commands and the MCP's tools are generated from the catalogue, or checked against it by a test. An operation added to the library then reaches all three, or the build fails.
The change is additive, so it does not wait for v3. Renaming amcli's commands is item 16 of #1019, and the catalogue would use the names that item settles.
🤖 Generated with Claude Code
Activity
Rafael-SOWNet commentedon Oct 22, 2026
A plan, before code
What exists today:
Transformation.Catalogue.csholds about twentyEntity -> Entitytransformations, each with its claim.Simplify,Expand,Factorize,Differentiate,IntegrateandLimitalready go through it.amclihas eight one-shot commands inOneShot.fs:eval simp fsimp diff solve sub latex info.Tools.cshas 23 tools, each with a routing description and guards of its own.The proposal. It is additive.
Queries. A
Querysits besideTransformation:Entity ->a set, a number, text or a table. It has a name, typed arguments and a one-line description. Solving, numerical evaluation, LaTeX, SymPy code, the truth table, the domain and the series become queries.One registry. It lists every transformation and query by name.
A test, not generation. The MCP descriptions are routing prompts, and its tools add guards, budgets and formatting that the library should not own. So both surfaces stay hand-written, and a test checks them against the registry:
am_check_steps;An entry added to the library then fails the build until a surface takes it or a list says why not.
Names. The test reads the entries' names, so it does not wait on Pending breakages: changes agreed or arguable that cannot ship before a major version #1019 item 16. That renaming changes one table when it comes.
Two questions for you:
TransformationinAngouriMath.Core.Transformations, or in a namespace of its own.Queryis public API in 2.7.0, or internal until v3.🤖 Generated with Claude Code
https://claude.ai/code/session_012sonx8iAspMiwRwokT1Ura