Writing packs by hand
A pack is a text file in TOML format, saved in the packs folder of SolutionMCP's settings folder with a name
ending in .toml. You can write one in any text editor. SolutionMCP picks up the change as soon as you save.
The tool editor writes exactly this format, so switching it to TOML is a good way to learn it.
A small pack
[pack]
name = "home"
description = "Tools for around the house"
[[tool]]
name = "weather"
description = "Short weather report for a city"
read_only = true
http = { url = "https://wttr.in/{{ city }}?format=3" }
[tool.params]
city = "City name"
[[tool]]
name = "disk_usage"
description = "Show how much space a folder uses"
read_only = true
command = ["du", "-sh", "{{ folder }}"]
[tool.params]
folder = { type = "path", description = "Folder to measure" }
The pack section
| Key | Meaning |
|---|---|
| name | The pack's name, shown on the Tools page. Default: the file name. |
| description | What the pack is for. |
| platforms | Load it only on these systems: macos, windows, linux, unix (Mac and Linux). |
| requires | Programs that must be installed for the pack to load, like ["ffmpeg"]. |
| [pack.prelude] | Code shared by the pack's scripts. See Shared code. |
Each tool
Every [[tool]] starts a new tool. The keys you'll use most:
| Key | Meaning |
|---|---|
| name | What the AI calls it. Letters, numbers, _ and -. |
| description | What it does, for the AI. |
| title | A friendlier name for people. |
| command, script, http or steps | What it runs: exactly one of these. |
| [tool.params] | Its parameters. A plain description means a required piece of text. |
| read_only | true if it only looks. |
| destructive | true if it can delete or overwrite. |
| confirm | true to always ask first, false to never ask. |
| runs_code | true if it runs whatever command or code it's given, like PowerShell. "Allow until restart" isn't offered for it unless you turn that on for commands. |
| timeout | Seconds before it's stopped. Default 60. |
| platforms, requires | Like the pack's, for just this tool. |
| output, format | What it returns. See What a tool returns. |
| cwd, env, stdin | The folder it runs in, extra environment variables, and text sent to its input. |
Parameters in full
[tool.params]
query = { type = "string", description = "What to search for", required = true }
limit = { type = "integer", default = 20, min = 1, max = 100 }
units = { type = "string", enum = ["metric", "imperial"], default = "metric" }
tags = { type = "array", items = "string", description = "Tags to apply" }
file = { type = "path", access = "write", description = "Where to save the report" }
Types are string, integer, number, boolean, array, object and path. enum lists the allowed values, and
access = "write" marks a path the tool writes to.
Check your work
- Mistakes show on the Tools page and on the Health check page, with the file and the problem.
- From a terminal,
solution-mcp config validatechecks every pack, andsolution-mcp call weather city=Denverruns a tool.
Important: In TOML, everything after a
[tool.params]or[[tool.steps]]line belongs to it, until the next[[tool]]. Put a tool's own keys, likeformat, before those lines.
See also Templates and quoting and Versions for each system.