kwork-mcp

Уведомления Kwork

list_notifications

Read-onlyIdempotent

Retrieve full notification groups and nested notifications from Kwork so you can review all alerts and updates in one place.

Instructions

Получить полные notification groups и вложенные notifications.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Default
`data`	No
`meta`	Yes
`error`	No
`summary`	Yes
`schema_version`	No	1.0
`knowledge_state`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.2.3Oct 3, 2026

addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "raw": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "type": "object"
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ],
+          "title": "Raw"
+        }
+      },
+      "required": [
+        "raw"
+      ],
+      "title": "RawObjectData",
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "enum": [
+            "auth_required",
+            "auth_expired",
+            "auth_in_progress",
+            "account_binding_required",
+            "account_mismatch",
+            "captcha",
+            "permission",
+            "ip_blocked",
+            "csrf",
+            "rate_limit",
+            "circuit_open",
+            "proxy",
+            "timeout",
+            "closed_project",
+            "duplicate",
+            "insufficient_connects",
+            "contract_drift",
+            "credential_update_unknown",
+            "ambiguous_write",
+            "idempotency_conflict",
+            "preparation_expired",
+            "invalid_confirmation",
+            "write_in_progress",
+            "write_disabled",
+            "not_found",
+            "validation",
+            "site_unsupported",
+            "site_mismatch",
+            "upstream_unavailable",
+            "internal"
+          ],
+          "title": "ErrorCode",
+          "type": "string"
+        },
+        "correlation_id": {
+          "title": "Correlation Id",
+          "type": "string"
+        },
+        "message": {
+          "title": "Message",
+          "type": "string"
+        },
+        "reconciliation_required": {
+          "default": false,
+          "title": "Reconciliation Required",
+          "type": "boolean"
+        },
+        "related_write_id": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Unresolved write that blocks this operation; reconcile it first.",
+          "title": "Related Write Id"
+        },
+        "retry_after_seconds": {
+          "anyOf": [
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Retry After Seconds"
+        },
+        "retryable": {
+          "default": false,
+          "title": "Retryable",
+          "type": "boolean"
+        },
+        "safe_to_retry": {
+          "default": false,
+          "title": "Safe To Retry",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code",
+        "message",
+        "correlation_id"
+      ],
+      "title": "ErrorInfo",
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedOutput schema / properties / knowledge_state

Added value: +{
+  "enum": [
+    "known_data",
+    "known_empty",
+    "unknown_error"
+  ],
+  "title": "KnowledgeState",
+  "type": "string"
+}

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "content_trust": {
+      "const": "external_untrusted",
+      "default": "external_untrusted",
+      "title": "Content Trust",
+      "type": "string"
+    },
+    "correlation_id": {
+      "title": "Correlation Id",
+      "type": "string"
+    },
+    "observed_at": {
+      "format": "date-time",
+      "title": "Observed At",
+      "type": "string"
+    },
+    "source": {
+      "const": "kwork",
+      "default": "kwork",
+      "title": "Source",
+      "type": "string"
+    },
+    "upstream_contract": {
+      "const": "kwork==0.2.0",
+      "default": "kwork==0.2.0",
+      "title": "Upstream Contract",
+      "type": "string"
+    }
+  },
+  "required": [
+    "observed_at",
+    "correlation_id"
+  ],
+  "title": "ResultMeta",
+  "type": "object"
+}

removedOutput schema / properties / result

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / schema_version

Added value: +{
+  "const": "1.0",
+  "default": "1.0",
+  "title": "Schema Version",
+  "type": "string"
+}

addedOutput schema / properties / summary

Added value: +{
+  "title": "Summary",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "knowledge_state",
+  "summary",
+  "meta"
+]

addedOutput schema / title

Added value: +"ResultEnvelope[RawObjectData]"

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.2.2Jun 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only a hint that results are grouped and nested, which duplicates the existing output schema and discloses nothing new (no read/unread semantics, no volume or pagination behavior).

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?

A single short sentence with no filler, and the core action is front-loaded. It is tight rather than verbose, though it borders on being too thin to be informative.

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

Completeness3/5

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

A zero-parameter read tool with an output schema is simple enough that return values need not be described, and the safety profile is in annotations. However, nothing about scope, ordering, or whether notifications are consumed/marked as read is stated, leaving moderate gaps for an agent deciding when and how often to call it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter information is missing because no parameters exist.

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?

States a specific verb ('Получить') and resource ('notification groups и вложенные notifications'), so an agent can tell it retrieves notifications in a grouped, nested shape. The domain term 'notification groups' is not explained and no scope is given, but the purpose is unambiguous and no sibling tool overlaps.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites and no mention of alternatives among the many list_* siblings. The agent must infer entirely from the tool name that this is the notification-listing entry point.

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