Memory history
get_memory_historyList a target's commits, newest first, with each memory region's used size and the change that commit made. Use it to see how memory evolved and to find the commits that grew it (the largest positive 'delta'); page back with 'offset'.
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": {
"project": "<project>",
"target": "<target>"
},
"name": "get_memory_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | Where to start: a full commit SHA, a SHA prefix (7+ characters), or a branch or tag name. Default: the head of the default branch. | |
| limit | No | Commits per page (default 30, max 200). | |
| offset | No | Commits to skip, for paging (default 0). | |
| region | No | Only this memory region, e.g. FLASH or RAM. | |
| target | Yes | Target name (see list_targets). | |
| project | Yes | The project: a public project's GitHub 'owner/repo' (no API key needed), or, with an API key, a project id or name from list_projects. | |
| only_changed | No | Skip commits whose build was identical to the previous one (default true). |