capture_calculate
Check the completion status, selected source and exact numeric summary. For prices 0.1 and 0.2 the expected sum is the decimal string "0.3".
tool · Connected client
Before you start
Capture one complete JSON response and copy its session ID. For the example below, the body needs an items array with a numeric price in each row. The calculation runs on the Mac; returning only the sum still requires access to the source body.
Access: Your MCP client needs the bodyRead capability for this tool.
Request
{
"name": "capture_calculate",
"arguments": {
"sessionIDs": [
"11111111-1111-4111-8111-111111111111"
],
"dataset": "responseJSON",
"selectionPointer": "/items",
"operation": {
"kind": "numericSummary",
"fieldPointer": "/price"
}
}
} sessionIDs- The explicit retained session IDs; use one complete response for responseJSON.
dataset- Use responseJSON for one JSON body or sessionMetadata for selected request metadata.
selectionPointer- JSON Pointer to the collection; /items selects the items array in this example.
operation- Choose a supported calculation. fieldPointer is relative to each selected row.
Illustrative tools/call parameters. Inspect the tool’s inputSchema in tools/list before sending them. Replace the synthetic UUID with the identifier from your own authorized session.
What to look for
Check the completion status, selected source and exact numeric summary. For prices 0.1 and 0.2 the expected sum is the decimal string "0.3".
If the result is unexpected
A sensitive-read grant is required. A removed body, changed source or incomplete selection is not a zero result. Select the intended complete capture again.
What to check if access is denied
Effects and cleanup
Reads the selected capture locally; it does not refetch the response, change the app or install a rule.
Same underlying tool: joesproxyctl capture calculate.
Browse all MCP reference entries →