MCP Multi-Chart Context
Compact context for MCP agents working across multiple charts.
Request body
Response
Successful calculation
Example response
{
"ok": true
}Changes
Changed in 4 of the 13 revisions of this API.6611
- ▲
the response property
data/summaries/items/became nullable for the status200response-property-became-nullable
- ▲
the
data/summaries/items/response's property type/format changed from/toobject/for status200response-property-type-changed
- ○
added the optional property
data/chartCountto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/contextHashto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/intentto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/notesto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/summaries/items/bigThreeto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/summaries/items/indexto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/summaries/items/nameto the response with the200statusresponse-optional-property-added
- ○
added the optional property
data/summaryStringto the response with the200statusresponse-optional-property-added
- ▲
- ○
added the new optional request property
inputs/items/ayanamsanew-optional-request-property
- ○
- ●
the
inputs/items/timezoneOffsetrequest property's max was set to14.00request-property-max-set
- ●
the
inputs/items/timezoneOffsetrequest property's min was set to-14.00request-property-min-set
- ●
- ▲
the request property
inputs/items/latitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
inputs/items/longitudebecame not nullablerequest-property-became-not-nullable
- ▲
the request property
inputs/items/latitudebecame requiredrequest-property-became-required
- ▲
the request property
inputs/items/longitudebecame requiredrequest-property-became-required
- ●
the
inputs/items/latituderequest property's max was set to90.00request-property-max-set
- ●
the
inputs/items/longituderequest property's max was set to180.00request-property-max-set
- ●
the
inputs/items/latituderequest property's min was set to-90.00request-property-min-set
- ●
the
inputs/items/longituderequest property's min was set to-180.00request-property-min-set
- ○
the
latituderequest property default value0was removedrequest-property-default-value-removed
- ○
the
longituderequest property default value0was removedrequest-property-default-value-removed
- ▲