One line over time
get_line_historyEvery recorded change to one projection, oldest first. Use an id from get_projections. Developer required. Free evaluation uses the fixed training-set sample.
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": {
"id": "<id>"
},
"name": "get_line_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Stable market id udm_<UUID> or priced line id udl_<UUID> where documented | |
| line | No | Restrict to an exact rung value | |
| after | No | Alias for cursor | |
| limit | No | Page size. Oversized valid limits are clamped. | |
| cursor | No | Cursor returned in meta.next_cursor | |
| line_type | No | Balanced main history by default; alternate or all explicitly | balanced |
| user_request | No | Optional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private. |