Skip to main content
Glama

read_entries

Read-onlyIdempotent

Fetch task case entries by number, type, or position with pagination, to review decisions, attempts, and other records in chronological order.

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
NameRequiredDescriptionDefault
keyYesTask 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`
nosNoOnly entries with these numbers
limitNoPage size. Without a value, the installation's default page size
typesNoOnly entries of these types
cursorNo`next_cursor` of the previous page; without it, the first page
after_noNoOnly entries filed after the entry with this number

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
next_cursorYesCursor of the next page, sent back as `cursor`; `null` means this page is the last one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed31 schema fields changedv0.5.2
    • 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"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses ordering ('in number order'), payload inclusion, AND-combination of filters, and the semantic content of decision/attempt entries, including failed attempts. That is genuinely useful behavioral context that the annotations and schema do not state.

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

Conciseness5/5

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

The main capability is front-loaded in the first sentence; the remaining paragraphs add filter semantics, type semantics, and the sibling alternative with no repetition or filler. Every sentence earns its place.

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

Completeness5/5

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

With a complete input schema, strong annotations, and an output schema, the description supplies the missing semantics: ordering, filter combination, type meanings, and the boundary with wait_journal. No critical behavioral or routing information is absent.

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 the baseline is 3. The description adds value by explaining how types and after_no combine under 'and' and by giving the meaning of decision/attempt entries, which goes beyond individual property descriptions. It does not need to restate key/limit/cursor.

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?

The description opens with a specific verb and resource: 'Returns entry bodies of one task's case, with payload, in number order.' This clearly separates it from wait_journal (many cases in one stream) and, by scope, from read_project_entries. The filter examples reinforce that this is the single-task entry reader.

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 explicitly routes multi-case streaming reads with waiting to wait_journal, and the filter examples ('types=... gives every summary', 'after_no...') teach how to narrow a call. It does not explicitly name read_project_entries as the project-wide alternative, though the 'one task's case' scope makes the boundary reasonably clear.

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