Casefile

Overview Schema Source Related Servers Discussions Admin

list_participants

Read-onlyIdempotent

List registered humans and permanent agents to identify possible addressees for questions. Temporary agents are excluded.

Instructions

Lists the participant registry: humans and permanent agents, the possible addressees of a question. Temporary agents are not registered and are absent from it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Page size. Without a value, the installation's default page size
`cursor`	No	`next_cursor` of the previous page; without it, the first page

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.

Changed10 schema fields changedv0.5.2Sep 25, 2026

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 / 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
-]
```

removedOutput schema / $defs / ParticipantKind

Removed value: -{
-  "description": "Род участника.\n\nРолей и прав за родом не стоит: любую запись и любой переход может сделать участник\nлюбого рода (`CONCEPT.md`, 3.1). Род нужен, чтобы читающий дело понимал, кто\nговорит, и чтобы интерфейс человека отличал людей от агентов в списке адресатов.",
-  "enum": [
-    "human",
-    "agent"
-  ],
-  "title": "ParticipantKind",
-  "type": "string"
-}

changedOutput schema / $defs / ParticipantView / description

Previous value: -"Участник реестра: кому можно адресовать вопрос и что о нём известно."New value: +"Registry participant: a possible addressee of a question."

removedOutput schema / $defs / ParticipantView / properties / kind / $ref
```
Removed value: -"#/$defs/ParticipantKind"
```

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

Added value: +"Kind of participant. It grants no rights: participants of either kind can make any entry and any transition"

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

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.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations by revealing the inclusion/exclusion rule for temporary agents and framing the registry as question addressees, which is not visible in the schema or annotations.

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 description is two sentences with no redundancy. The primary purpose is front-loaded, and the temporary-agent exclusion earns its place by adding scoping information that is essential for correct usage.

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?

For a simple read-only list tool with fully documented optional pagination parameters, an output schema, and strong annotations, nothing essential is missing. The description covers the domain context and the key exclusion rule, making the tool's behavior predictable.

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?

Schema description coverage is 100% for both parameters (limit and cursor), so the description carries no additional parameter burden. The baseline of 3 applies; the description adds no special semantics beyond what the schema already documents.

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 states a specific verb and resource ('Lists the participant registry') and precisely defines the scope: humans and permanent agents who are possible addressees. It also distinguishes itself from register/update_participant by clarifying what is listed versus what is maintained.

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?

The description clarifies when this tool is appropriate: to view the registry of possible question addressees, and it explicitly notes that temporary agents are absent. While it doesn't name alternative tools or exclusion conditions explicitly, the scope is clear enough for an agent to choose it over participant mutation tools.

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