Casefile

Overview Schema Source Related Servers Discussions Admin

Read case entries

read_entries

Read-onlyIdempotent

Retrieves case entries for a task, including payloads, in number order. Filter by type, number, or after a given entry to inspect decisions, attempts, and more.

Instructions

Returns entry bodies of one task's case, with payload, in number order.

Filters combine with and: types=["summary"] gives every summary, after_no everything filed after the named entry, and both together the entries of those types filed after it. decision and attempt entries hold the choices already made and the attempts already tried, failed ones included.

Entries of many cases in one stream, with a wait for new ones, come from wait_journal.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`
`nos`	No	Only entries with these numbers
`limit`	No	Page size. Without a value, the installation's default page size
`types`	No	Only entries of these types
`cursor`	No	`next_cursor` of the previous page; without it, the first page
`after_no`	No	Only entries filed after the entry with this number

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`next_cursor`	Yes	Cursor of the next page, sent back as `cursor`; `null` means this page is the last one

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.1Oct 6, 2026

changedInput schema / properties / types / anyOf

Previous value: -[
-  {
-    "items": {
-      "description": "Case entry type. Types up to `note` are written by agents and humans; the types after it are filed by the tracker itself with the change they record",
-      "enum": [
-        "summary",
-        "decision",
-        "attempt",
-        "finding",
-        "artifact",
-        "question",
-        "answer",
-        "verdict",
-        "remark",
-        "resolution",
-        "note",
-        "created",
-        "status_changed",
-        "section_changed",
-        "field_changed",
-        "assignee_changed",
-        "link_added",
-        "link_removed",
-        "moved",
-        "attribute_created",
-        "attribute_changed",
-        "attribute_removed",
-        "archived",
-        "restored"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Case entry type. Types up to `note` are written by agents and humans; the types after it are filed by the tracker itself with the change they record",
+      "enum": [
+        "summary",
+        "decision",
+        "attempt",
+        "finding",
+        "artifact",
+        "question",
+        "answer",
+        "verdict",
+        "remark",
+        "resolution",
+        "acceptance",
+        "note",
+        "created",
+        "status_changed",
+        "section_changed",
+        "field_changed",
+        "assignee_changed",
+        "link_added",
+        "link_removed",
+        "moved",
+        "warning",
+        "attribute_created",
+        "attribute_changed",
+        "attribute_removed",
+        "archived",
+        "restored"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / $defs / EntryView / properties / type / enum

Previous value: -[
-  "summary",
-  "decision",
-  "attempt",
-  "finding",
-  "artifact",
-  "question",
-  "answer",
-  "verdict",
-  "remark",
-  "resolution",
-  "note",
-  "created",
-  "status_changed",
-  "section_changed",
-  "field_changed",
-  "assignee_changed",
-  "link_added",
-  "link_removed",
-  "moved",
-  "attribute_created",
-  "attribute_changed",
-  "attribute_removed",
-  "archived",
-  "restored"
-]New value: +[
+  "summary",
+  "decision",
+  "attempt",
+  "finding",
+  "artifact",
+  "question",
+  "answer",
+  "verdict",
+  "remark",
+  "resolution",
+  "acceptance",
+  "note",
+  "created",
+  "status_changed",
+  "section_changed",
+  "field_changed",
+  "assignee_changed",
+  "link_added",
+  "link_removed",
+  "moved",
+  "warning",
+  "attribute_created",
+  "attribute_changed",
+  "attribute_removed",
+  "archived",
+  "restored"
+]

Changed31 schema fields changedv0.5.2Sep 25, 2026

removedInput schema / $defs

Removed value: -{
-  "EntryType": {
-    "description": "Тип записи дела. Записи агента и человека — до `NOTE`, служебные — после.",
-    "enum": [
-      "summary",
-      "decision",
-      "attempt",
-      "finding",
-      "artifact",
-      "question",
-      "answer",
-      "verdict",
-      "remark",
-      "resolution",
-      "note",
-      "created",
-      "status_changed",
-      "section_changed",
-      "field_changed",
-      "assignee_changed",
-      "link_added",
-      "link_removed"
-    ],
-    "title": "EntryType",
-    "type": "string"
-  }
-}

changedInput schema / properties / after_no / description

Previous value: -"Только записи после этого номера — что случилось с тех пор"New value: +"Only entries filed after the entry with this number"

removedInput schema / properties / after_no / examples
```
Removed value: -[
-  12
-]
```

changedInput schema / properties / cursor / description

Previous value: -"Продолжение выдачи: значение `next_cursor` из прошлого ответа"New value: +"`next_cursor` of the previous page; without it, the first page"

changedInput schema / properties / key / description

Previous value: -"Ключ задачи, например `TRK-42`. Регистр не важен"New value: +"Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`"

changedInput schema / properties / limit / description

Previous value: -"Сколько записей вернуть за раз. Без значения — размер страницы установки"New value: +"Page size. Without a value, the installation's default page size"

removedInput schema / properties / limit / examples
```
Removed value: -[
-  25
-]
```

changedInput schema / properties / nos / description

Previous value: -"Только эти номера записей"New value: +"Only entries with these numbers"

removedInput schema / properties / nos / examples

Removed value: -[
-  [
-    3,
-    12
-  ]
-]

changedInput schema / properties / types / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/EntryType"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "Case entry type. Types up to `note` are written by agents and humans; the types after it are filed by the tracker itself with the change they record",
+      "enum": [
+        "summary",
+        "decision",
+        "attempt",
+        "finding",
+        "artifact",
+        "question",
+        "answer",
+        "verdict",
+        "remark",
+        "resolution",
+        "note",
+        "created",
+        "status_changed",
+        "section_changed",
+        "field_changed",
+        "assignee_changed",
+        "link_added",
+        "link_removed",
+        "moved",
+        "attribute_created",
+        "attribute_changed",
+        "attribute_removed",
+        "archived",
+        "restored"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / types / description

Previous value: -"Только записи этих типов"New value: +"Only entries of these types"

removedInput schema / properties / types / examples

Removed value: -[
-  [
-    "decision",
-    "attempt"
-  ]
-]

removedOutput schema / $defs / AuthorKind

Removed value: -{
-  "description": "Кто именно сделал действие.\n\n`tracker` — сам трекер: этим родом подписаны служебные записи дела и строки,\nзаведённые командой первичной инициализации. У него нет подписи, потому что\nназывать себя по имени ему незачем: трекер в установке один.",
-  "enum": [
-    "agent",
-    "human",
-    "tracker"
-  ],
-  "title": "AuthorKind",
-  "type": "string"
-}

changedOutput schema / $defs / AuthorView / description

Previous value: -"Кто сделал действие: род и подпись. У самого трекера подписи нет."New value: +"Who acted: kind and signature. The tracker itself has no signature."

removedOutput schema / $defs / AuthorView / properties / kind / $ref
```
Removed value: -"#/$defs/AuthorKind"
```

addedOutput schema / $defs / AuthorView / properties / kind / description

Added value: +"Kind of author. `tracker` signs the service entries the tracker files itself"

addedOutput schema / $defs / AuthorView / properties / kind / enum
```
Added value: +[
+  "agent",
+  "human",
+  "tracker"
+]
```
addedOutput schema / $defs / AuthorView / properties / kind / type
```
Added value: +"string"
```

removedOutput schema / $defs / EntryType

Removed value: -{
-  "description": "Тип записи дела. Записи агента и человека — до `NOTE`, служебные — после.",
-  "enum": [
-    "summary",
-    "decision",
-    "attempt",
-    "finding",
-    "artifact",
-    "question",
-    "answer",
-    "verdict",
-    "remark",
-    "resolution",
-    "note",
-    "created",
-    "status_changed",
-    "section_changed",
-    "field_changed",
-    "assignee_changed",
-    "link_added",
-    "link_removed"
-  ],
-  "title": "EntryType",
-  "type": "string"
-}

changedOutput schema / $defs / EntryView / description

Previous value: -"Запись дела целиком.\n\n`payload` — единственное поле слоя без объявленной формы, и это то же исключение,\nчто и в схеме REST (`docs/notes/api.md`, «`payload` записи дела — исключение из\nтипизации, названное по месту»): нагрузка своя у каждого типа записи, и типизирует\nеё отдельная задача — сразу в обоих интерфейсах, иначе они разойдутся. `JsonValue`,\nа не `Any`: форма свободна, но значение обязано быть представимо в JSON."New value: +"Case entry in full."

addedOutput schema / $defs / EntryView / properties / project_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Key of the owning project for an entry of a project's case (`TRK#7`); `null` for a task entry",
+  "title": "Project Key"
+}

addedOutput schema / $defs / EntryView / properties / seq / description

Added value: +"Journal sequence number, usable as `after` of `wait_journal`"

addedOutput schema / $defs / EntryView / properties / task_key / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / $defs / EntryView / properties / task_key / description

Added value: +"Key of the owning task; `null` for an entry of a project's case"

removedOutput schema / $defs / EntryView / properties / task_key / type
```
Removed value: -"string"
```
removedOutput schema / $defs / EntryView / properties / type / $ref
```
Removed value: -"#/$defs/EntryType"
```

addedOutput schema / $defs / EntryView / properties / type / description

Added value: +"Case entry type. Types up to `note` are written by agents and humans; the types after it are filed by the tracker itself with the change they record"

addedOutput schema / $defs / EntryView / properties / type / enum

Added value: +[
+  "summary",
+  "decision",
+  "attempt",
+  "finding",
+  "artifact",
+  "question",
+  "answer",
+  "verdict",
+  "remark",
+  "resolution",
+  "note",
+  "created",
+  "status_changed",
+  "section_changed",
+  "field_changed",
+  "assignee_changed",
+  "link_added",
+  "link_removed",
+  "moved",
+  "attribute_created",
+  "attribute_changed",
+  "attribute_removed",
+  "archived",
+  "restored"
+]

addedOutput schema / $defs / EntryView / properties / type / type
```
Added value: +"string"
```

changedOutput schema / $defs / EntryView / required

Previous value: -[
-  "id",
-  "seq",
-  "no",
-  "task_key",
-  "type",
-  "author",
-  "title",
-  "body",
-  "payload",
-  "refs",
-  "created_at"
-]New value: +[
+  "id",
+  "seq",
+  "no",
+  "task_key",
+  "project_key",
+  "type",
+  "author",
+  "title",
+  "body",
+  "payload",
+  "refs",
+  "created_at"
+]

addedOutput schema / properties / next_cursor / description

Added value: +"Cursor of the next page, sent back as `cursor`; `null` means this page is the last one"

First observedSep 23, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds genuine domain context beyond them: `decision` and `attempt` entries record choices already made and attempts already tried, including failed ones. It does not discuss paging or result shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core behavior and scoping, then a tightly written sentence on filter combination, then a one-line pointer to the sibling. The two filter examples are slightly more elaborate than strictly needed, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 params, full schema coverage, an output schema, and safety annotations, the description only needs to carry filtering and routing semantics, which it does. It is complete enough to call correctly and only marginally omits anything an agent would want.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics the schema lacks: how `types` and `after_no` compose ('both together the entries of those types filed after it'), with a concrete example. That is value beyond the field-level descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Returns entry bodies of one task's case, with payload, in number order'), which distinguishes it from search_tasks and roughly from read_project_entries via the 'one task's case' scoping. It stops short of explicitly naming the read_project_entries sibling it is most easily confused with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It routes the agent to `wait_journal` for the opposite need (streaming many cases plus waiting for new entries), and spells out how filters combine with `and`. There is no explicit 'when not to use this' beyond that routing hint, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.