kwork-mcp

Профиль пользователя Kwork

get_user_info

Read-onlyIdempotent

Retrieve a Kwork user's full public profile by providing exactly one identifier: user ID or username. This returns profile details for a single user.

Instructions

Получить полный публичный профиль ровно по одному user_id или username.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	No
`username`	No

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.

Changed13 schema fields changedv0.2.3Oct 3, 2026

changedInput schema / properties / user_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / username / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 64,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

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

addedOutput schema / properties / data

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "raw": {
+          "additionalProperties": {},
+          "title": "Raw",
+          "type": "object"
+        },
+        "user_id": {
+          "title": "User Id",
+          "type": "integer"
+        },
+        "username": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Username"
+        }
+      },
+      "required": [
+        "user_id",
+        "raw"
+      ],
+      "title": "UserRecord",
+      "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[UserRecord]"

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=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the profile returned is public and that the lookup is by a single identifier, which is modest added context but nothing about rate limits, auth, or missing-user behavior.

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 front-loaded sentence with no filler; the constraint ('ровно по одному') is placed immediately after the resource so it is read before the agent inspects parameters.

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?

An output schema exists, so return-value documentation is not required. Still, with 0% schema description coverage and two undocumented parameters, the description should do more to specify acceptable identifier formats and behavior when a user is not found.

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 coverage is 0%, so the description carries the burden. It does convey the key semantic the schema cannot express: exactly one of user_id or username must be supplied, even though both are nullable with default null in the schema. It adds no format details (e.g. integer bounds, username length/character rules) for either parameter.

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 ('полный публичный профиль') with a clear scope qualifier ('ровно по одному user_id или username'). It does not name a sibling such as search_users, but the 'exact single lookup' framing implicitly distinguishes it from search-style tools.

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

Usage Guidelines3/5

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

The phrase 'ровно по одному' gives an important usage rule — pass exactly one identifier, not both — which is genuinely actionable. However, there is no guidance on when to prefer this tool over search_users or other profile-adjacent siblings, and no stated prerequisites.

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