Casefile

Overview Schema Source Related Servers Discussions Admin

Read project entries

read_project_entries

Read-onlyIdempotent

Fetch a project's case entry bodies, including payloads, ordered by entry number. Filter by type, attribute history, or entry range to review decisions, findings, artifacts, and notes.

Instructions

Returns the bodies of a project's case entries, payload included, ordered by entry number.

The project's case holds decisions, findings, artifacts and notes about the project, and the tracker's own entries about its card. Filters combine with and, as in read_entries. attribute gives one attribute's history: attribute_created, attribute_changed, attribute_removed entries with that name. The case index, titles only, comes with get_project.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Project key, case-insensitive. An unknown key is refused with `project_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
`attribute`	No	Only entries about the attribute with this name: `attribute_created`, `attribute_changed`, `attribute_removed`; matching ignores case

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"
+]

Addedv0.5.2Sep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real behavioral context: results are ordered by entry number, payloads are included, filters AND together, and `attribute` narrows to created/changed/removed entries. Pagination mechanics are left to the schema.

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 in the first sentence, followed by scoping and filter semantics. Every sentence carries information, though the middle sentence is dense and packs several distinct facts into one block.

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?

An output schema exists, so return values need not be described, and the description covers what the case holds versus tracker entries, ordering, filtering and the index alternative. Minor gaps remain around pagination interplay and default page size, but the essential call-shaping information is present.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema by explaining that filters combine with `and` and that `attribute` returns the attribute's creation/change/removal history. It does not clarify how `nos`, `after_no`, `cursor` and `limit` interact, so it is above baseline but not exhaustive.

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

Purpose5/5

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

States a specific verb and resource ('Returns the bodies of a project's case entries, payload included, ordered by entry number') and immediately scopes it against siblings: the case index with titles only comes with `get_project`, and filter semantics mirror `read_entries`. An agent can distinguish this from `get_project` and `read_entries` without opening any schema.

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?

Gives clear routing context ('The case index, titles only, comes with `get_project`') and explains that filters combine with `and`, plus the special semantics of `attribute`. It does not explicitly state when to prefer this over `read_entries` beyond the filter-semantics reference, so it stops short of full when/when-not guidance.

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