Casefile

Overview Schema Source Related Servers Discussions Admin

ask

Record a question for task participants, optionally blocking progress. It remains open until an answer is filed, tracking open and blocking question counts.

Instructions

Files a question to registry participants. The tracker delivers nothing: an addressee sees the question when reading the feed or their inbox.

A question stays open until an answer with its number is filed in the same task; it counts toward open_questions, and with blocking toward open_blocking_questions.

What the cases of the parent, its ancestors and sibling tasks already record is readable through get_task and read_entries, without a question.

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`
`body`	No	Entry body in markdown, stored and returned as is. It holds what a successor needs to continue; file contents and long outputs stay outside it, represented by a pointer and the gist
`title`	Yes	Entry title: its line in the case index of `get_task`. It states what happened, not how
`blocking`	Yes	Whether work on the task can go on without the answer. `true` counts toward the `open_blocking_questions` feature, by which such tasks are selected; the tracker does nothing else with it
`addressees`	Yes	Names of participants from `list_participants`, at least one. A temporary agent has no registry entry and cannot be addressed. An unknown name is refused with `entry_fields_invalid`, `reason: unknown_participant`
`idempotency_key`	No	Retry key chosen by the caller, e.g. a UUID. A repeat with the same key and the same arguments returns the first result and creates nothing; the same key with other arguments is refused with `idempotency_key_reused`. A key is bound to the caller's token and kept for 24 hours

Output Schema

TableJSON Schema

Name	Required	Description
`no`	Yes	Entry number in the task's case; with the key it forms `TRK-42#12`
`seq`	Yes	Journal sequence number, usable as `after` of `wait_journal`
`title`	Yes	The title the tracker built, for entry types whose title is not sent (summary, answer, verdict, resolution, service entries); `null` when the caller sent the title
`author`	Yes
`task_key`	Yes
`created_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.5.2Sep 25, 2026

changedInput schema / properties / addressees / description

Previous value: -"Имена участников из `list_participants`, хотя бы одно. Временного агента адресовать нельзя: строки в реестре у него нет"New value: +"Names of participants from `list_participants`, at least one. A temporary agent has no registry entry and cannot be addressed. An unknown name is refused with `entry_fields_invalid`, `reason: unknown_participant`"

removedInput schema / properties / addressees / examples
```
Removed value: -[
-  [
-    "owner"
-  ]
-]
```

changedInput schema / properties / blocking / description

Previous value: -"Можно ли продолжать работу без ответа. Значения по умолчанию нет намеренно: это знаешь только ты. `true` считается признаком `open_blocking_questions`, по которому задачу находят отбором; больше трекер с ним ничего не делает"New value: +"Whether work on the task can go on without the answer. `true` counts toward the `open_blocking_questions` feature, by which such tasks are selected; the tracker does nothing else with it"

removedInput schema / properties / blocking / examples
```
Removed value: -[
-  true
-]
```

changedInput schema / properties / body / description

Previous value: -"Тело записи в markdown; хранится и отдаётся как есть"New value: +"Entry body in markdown, stored and returned as is. It holds what a successor needs to continue; file contents and long outputs stay outside it, represented by a pointer and the gist"

changedInput schema / properties / idempotency_key / description

Previous value: -"Ключ повтора, который ты придумываешь сам (обычно UUID). Повтор вызова с тем же ключом и теми же аргументами отвечает первым результатом и второго объекта не заводит; тот же ключ с другими аргументами отклоняется. Ключ живёт в паре с твоим токеном и помнится 24 часа"New value: +"Retry key chosen by the caller, e.g. a UUID. A repeat with the same key and the same arguments returns the first result and creates nothing; the same key with other arguments is refused with `idempotency_key_reused`. A key is bound to the caller's token and kept for 24 hours"

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 / title / description

Previous value: -"Заголовок записи: он стоит в описи дела, которую отдаёт `get_task`"New value: +"Entry title: its line in the case index of `get_task`. It states what happened, not how"

removedInput schema / properties / title / examples

Removed value: -[
-  "Выбран asyncpg вместо psycopg: нужен LISTEN без потока"
-]

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"
```

changedOutput schema / description

Previous value: -"Ответ подшивающего инструмента: чем запись адресуют, без самой записи.\n\n`title` непуст только там, где заголовок собрал трекер: у сводки, ответа, вердикта и\nрезолюции его не принимают вовсе (`app/domain/case.py`, `TITLED_ENTRY_TYPES`). Где\nзаголовок прислал агент, здесь стоит `null` — «в описи ровно то, что ты прислал»."New value: +"A filed entry, by its address rather than its content; the entry in full is\nreturned by `read_entries`."

addedOutput schema / properties / no / description

Added value: +"Entry number in the task's case; with the key it forms `TRK-42#12`"

addedOutput schema / properties / seq / description

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

addedOutput schema / properties / title / description

Added value: +"The title the tracker built, for entry types whose title is not sent (summary, answer, verdict, resolution, service entries); `null` when the caller sent the title"

First observedSep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations are all false, so the description carries the burden and does so well. It discloses that no delivery happens ('the tracker delivers nothing'), that questions count toward `open_questions`/`open_blocking_questions`, and that they stay open until answered.

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?

Three short paragraphs, with the core action in the first sentence and no filler. The additional sentences each add distinct information: delivery behavior, lifecycle/counters, and read alternatives.

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?

Given the rich schema and the presence of an output schema, the description covers all non-obvious behavioral context: no notification, lifecycle, counters, and when to use read tools instead. No important decision-relevant behavior is missing.

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

Parameters3/5

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

The schema already documents every parameter with detailed descriptions, and the input schema coverage is 100%. The description adds a little lifecycle context around `blocking`, but does not need to compensate for schema gaps.

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 first sentence names a specific action and resource ('Files a question to registry participants'), and the rest clarifies lifecycle and counters. It distinguishes itself from the sibling `answer` by explaining a question remains open until an answer is filed, and from read tools by noting existing records are readable without asking.

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

Usage Guidelines5/5

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

It explicitly names `get_task` and `read_entries` as alternatives when the information is already recorded ('without a question'). It also explains the question lifecycle with `answer`, giving the agent a clear condition for when a follow-up tool is needed.

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

ask

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools