kwork-mcp

Детали кворка

get_kwork_details

Read-onlyIdempotent

Retrieves the full getKworkDetailsExtra response for a Kwork listing by kwork_id, filtering out false fields.

Instructions

Получить полный getKworkDetailsExtra response без ложных полей.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kwork_id`	Yes

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.

Changed12 schema fields changedv0.2.3Oct 3, 2026

addedInput schema / properties / kwork_id / exclusiveMinimum
```
Added value: +0
```
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

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered structurally. The phrase 'без ложных полей' ('without false fields') hints that the response is returned faithfully without fabricated fields, but this is cryptic and does not clearly state what behavior it guarantees.

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

Conciseness3/5

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

One sentence, front-loaded, no wasted words. But its brevity reflects under-specification rather than tightness, so it earns only a middling score.

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

Completeness2/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 explained. But for a detail-fetch tool whose entire purpose rests on an opaque internal type name, and with a required parameter left undocumented, the description is too thin to orient the agent.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter kwork_id is documented nowhere. The description adds no meaning about the parameter's format or constraints, so it fails to compensate for the schema gap.

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

Purpose3/5

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

The verb+resource ('Получить ... getKworkDetailsExtra response') indicate a detail-fetch for a kwork, which is somewhat clear against siblings like get_order_details. However, the object is described by an opaque internal type name ('getKworkDetailsExtra') rather than plain language, so the agent must infer what a 'kwork detail' contains.

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 statement of when to use this versus list_my_kworks, get_order_details, or get_project. No prerequisites, no exclusions, no alternatives are named. The agent gets zero routing guidance.

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