kwork-mcp

Баланс коннектов Kwork

get_connects

Read-onlyIdempotent

Fetch active and shared Kwork connects without modifying your account. Check available response credits before bidding on projects.

Instructions

Получить активные и общие коннекты без изменения аккаунта.

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": {
+        "active": {
+          "title": "Active",
+          "type": "integer"
+        },
+        "raw": {
+          "additionalProperties": {},
+          "title": "Raw",
+          "type": "object"
+        },
+        "total": {
+          "title": "Total",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "active",
+        "total",
+        "raw"
+      ],
+      "title": "ConnectsData",
+      "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[ConnectsData]"

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

First observedv0.2.2Jun 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the scope of returned data ('активные и общие коннекты') but otherwise duplicates the read-only annotation and says nothing about rate limits, auth, or freshness.

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?

A single short sentence with the verb and scope front-loaded and zero filler. Nothing can be trimmed without losing meaning.

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

Completeness4/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 described, and annotations cover the behavioral profile; zero parameters means no argument documentation is needed. The definition is nearly complete, with only minor ambiguity about what 'общие' (total) connects measure.

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 per the rubric the baseline is 4. There is no parameter meaning the description could or should add.

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 ('коннекты') with scope ('активные и общие'), so an agent knows it fetches connects. No sibling tool overlaps this resource, so no explicit differentiation is required, but it is not maximally precise about the returned shape.

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 tool versus alternatives, nor any prerequisite or trigger condition. 'без изменения аккаунта' hints that it is a safe read, but that is a property, not usage guidance.

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