config-migration
Migrate a v1 config to a v2 schema with an explicit mapping, and list what was dropped or defaulted — Applies a declared mapping (from pointer, to pointer, optional transform such as string-to-number or a value map) to a v1 JSON config, carries over unmapped keys the v2 schema declares, fills schema defaults, validates the result against the v2 JSON Schema 2020-12 and returns the migrated config plus three exact lists: dropped (v1 values that landed nowhere, with their JSON pointers), defaulted (v
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": {
"v1": "<v1>",
"v2Schema": "<v2Schema>",
"mapping": "<mapping>"
},
"name": "config-migration"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| v1 | Yes | The old config (any JSON value). | |
| mapping | Yes | ||
| v2Schema | Yes | The new config's schema. Full JSON Schema 2020-12 (local $ref only). | |
| applyDefaults | No | Fill missing v2 properties from schema defaults (default true). | |
| carryDeclared | No | Copy unmapped v1 values to the same pointer when v2 declares that property (default true). |