save_layer
Persist an inferred semantic layer as a file in your repository so teammates and later sessions share the same business context instead of a per-machine cache.
Instructions
Write the layer into the user's project so their team has it.
The cache is per-machine; a file in the repository is what a
colleague reads. From then on this session's verdicts land there.
Ask where they want it rather than choosing for them. A file already
at that path is replaced; a path that cannot be written comes back
as `saved: false` with the reason.
Refused on a set: a hub and its members are several files the user
already chose the paths for, and one file cannot hold them.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"path": "<path>"
},
"name": "save_layer"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Where to write the layer file, as the user chose it: for example `semantic/layer.yaml` in their repository. `~` is expanded and missing folders are created. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |