kwork-mcp

Детали оффера Kwork

get_offer

Read-onlyIdempotent

Retrieve your own Kwork offer by offer_id and required project_id to review its details and project context.

Instructions

Получить собственный оффер по offer_id, включая обязательный project_id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`offer_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 / offer_id / exclusiveMinimum
```
Added value: +0
```
addedOutput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "created_at": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Created At"
+        },
+        "description": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Description"
+        },
+        "duration_days": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Duration Days"
+        },
+        "offer_id": {
+          "title": "Offer Id",
+          "type": "integer"
+        },
+        "price": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Price"
+        },
+        "project_id": {
+          "title": "Project Id",
+          "type": "integer"
+        },
+        "raw": {
+          "additionalProperties": {},
+          "title": "Raw",
+          "type": "object"
+        },
+        "status": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Status"
+        },
+        "title": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Title"
+        }
+      },
+      "required": [
+        "offer_id",
+        "project_id",
+        "raw"
+      ],
+      "title": "OfferRecord",
+      "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[OfferRecord]"

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

First observedv0.2.2Jun 23, 2026

TDQS

C2.6/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 by structured data. The description adds only the 'own offer' scoping and otherwise contributes no behavioral context such as error conditions, auth requirements, or what happens when the offer is inaccessible.

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?

The description is a single front-loaded sentence, which is appropriately sized. However, the closing clause about the 'mandatory project_id' does not earn its place because it references a parameter that does not exist in the schema and only adds confusion.

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 the description is still incomplete: it gives no sibling routing and introduces a schema-inconsistent parameter claim that could mislead an agent about how to call the tool. For a simple 1-parameter lookup it should at minimum be accurate.

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 sole parameter offer_id is documented nowhere in the schema, so the description must compensate — but it only names the field without format or meaning. Worse, it asserts that a 'mandatory project_id' is involved, yet the schema declares only offer_id as required and sets additionalProperties=false, so project_id cannot even be supplied.

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?

The description states a specific verb and resource ('Получить собственный оффер по offer_id') and scopes it to the caller's own offer, which distinguishes it somewhat from a generic offer lookup. However, it never contrasts itself with close siblings like list_my_offers or get_kwork_details, so the agent still has to guess which retrieval tool applies.

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 statement of prerequisites, and no routing to alternatives despite several overlapping siblings. The phrase 'собственный оффер' hints at scope but is not an explicit usage rule.

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