Tool reference · Knowledge graph & temporal facts
kg_timeline
Returns every fact ever recorded for a subject in chronological order, including ones that were later replaced or closed.
local stdio server read-only
When to use
- You want to see how a decision evolved over time.
- You want to know when and why a fact was replaced.
- You are writing a changelog or architecture history.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
subjectrequired | string | — | — |
predicate | string | — | — |
project | string | — | — |
limit | integer | 500 | — |
Example
Arguments
{
"subject": "my-api",
"predicate": "uses_queue"
}Result shape
{
"count": 2,
"timeline": [
{
"id": "1a2b3c4d5e6f47089a0b1c2d3e4f5a6b",
"predicate": "uses_queue",
"object": "redis",
"valid_from": "2025-11-02T09:00:00Z",
"valid_to": "2026-06-10T14:21:00Z"
},
{
"id": "5e0b7d2c9a1f4e3b8c6d0a2f4b6e8c1d",
"predicate": "uses_queue",
"object": "rabbitmq",
"valid_from": "2026-06-10T14:21:00Z",
"valid_to": null
}
]
}Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
Full chronological history of assertions for a subject.