mathematica-skill
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mathematica_doctorC | 检测 Wolfram 内核、许可证、前端和 wolframscript。 |
| mathematica_planB | 解析任务 JSON 并返回执行计划,不启动 Mathematica。 |
| mathematica_lintC | 静态检查 Wolfram Language 语法与高风险调用。 |
| mathematica_buildC | 生成原生 .nb 和 .wl;draft=true 时不要求 Mathematica。 |
| mathematica_runC | 跑完整流水线:预检、原生执行、导出、重开复算、对账、交付。 |
| mathematica_computeA | 在真实 Wolfram 内核里执行一段代码,返回最后一个表达式的值和消息;图形结果可导出 PNG。快速计算,不做 checks、Notebook 和复算,因此永远 verified=false;可交付成果请用 mathematica_run。 |
| mathematica_evaluate_notebookC | 用桌面前端执行已有 .nb 并返回结果。 |
| mathematica_edit_notebookA | 在既有 .nb 上做定点修改(替换/插入/追加单元、改标题、翻转标题语言),默认另存新文件,写入后回读校验编码,不会产生乱码。 |
| mathematica_exportC | 从真实 Wolfram 图形导出 PNG/PDF/CSV。 |
| mathematica_verifyC | 在干净内核中重新执行 checks 并与参考结果比较。 |
| mathematica_exampleA | 返回一个可运行的示例任务 JSON。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a distinct role in the Mathematica workflow, and descriptions explicitly distinguish quick execution (mathematica_compute) from full verified pipelines (mathematica_run). However, mathematica_run orchestrates execution, export, and verification, creating intentional overlap with mathematica_compute, mathematica_export, and mathematica_verify that could still cause hesitation between single-step and full-pipeline tools.
All tools follow the same mathematica_ prefix with lowercase verb or noun names, such as mathematica_run, mathematica_export, and mathematica_edit_notebook. The convention is predictable and consistent throughout.
Eleven tools is well within the ideal range and fits the multi-stage nature of Mathematica diagnostics, planning, building, execution, notebook editing, export, and verification. Each tool appears to earn its place rather than bloating the surface.
The surface covers a full workflow from environment diagnostics and planning through linting, building, running, notebook evaluation/editing, exporting, and verification, plus a sample-task helper. Minor gaps remain around notebook or task inventory/cleanup operations, but core lifecycle needs are well covered.