Skip to main content
Glama
wirk-mcp

wirk-mcp

Official
by wirkspace

wirk_write

Idempotent

Apply or propose atomic batches of item edits, links, archives, and messages with revision checks, so conflicting changes are caught before data is written.

Instructions

Change items and links atomically. In expect put each changed or linked-from item’s rN and the parent work of a contributes_to link; missing revisions get basis_changed. Context changes apply when you may make them; requires_review means propose with a reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operations": "<operations>"
    },
    "name": "wirk_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
expectNo{"<ID>": <revision you read>}.
formatNo
reasonNoWhy: required to propose and to archive; to complete wirk, the evidence (tests, link, file path or upload ID).
operationsYes1-32 of: {op:item.create, ref?, data:{title, body?, owner?, work?:{owner_id? (me or an ID), due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, owner?, work?, fields?, reservation?, attach_uploads?}}; reservation occupied starts; occupied:G guards any edit; vacant:G releases; replace:G takes over (a reviewer, with a reason, when a person asks) · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites link also takes target_revision, selector, relation and quotation: the exact text, else quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}}; a board post adds link.create related_to from its $ref to the item · {op:message.acknowledge, messages:[ID]}. owner: a record's owner; on work, work.owner_id. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written.
request_idNoNamed in the receipt; set your own when attaching files. After an uncertain result, resend with that ID.
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.34
    • changedInput schema / properties / expect / description
      Previous value: -"{\"<ID>\": <revision you read>}, e.g. {\"5c1e7a90\": 3}."New value: +"{\"<ID>\": <revision you read>}."
    • changedInput schema / properties / operations / description
      Previous value: -"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id? (me or an ID), due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?, reservation?, attach_uploads?}}; reservation occupied starts; occupied:G guards any edit; vacant:G releases; replace:G takes over (a reviewer, with a reason, when a person asks) · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites link also takes target_revision, selector, relation and quotation: the exact text, else quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}}; a board post adds link.create related_to from its $ref to the item · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written."New value: +"1-32 of: {op:item.create, ref?, data:{title, body?, owner?, work?:{owner_id? (me or an ID), due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, owner?, work?, fields?, reservation?, attach_uploads?}}; reservation occupied starts; occupied:G guards any edit; vacant:G releases; replace:G takes over (a reviewer, with a reason, when a person asks) · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites link also takes target_revision, selector, relation and quotation: the exact text, else quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}}; a board post adds link.create related_to from its $ref to the item · {op:message.acknowledge, messages:[ID]}. owner: a record's owner; on work, work.owner_id. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written."
    • changedInput schema / properties / request_id / description
      Previous value: -"Optional; named in the receipt; set your own when attaching files. After an uncertain result, resend with that ID."New value: +"Named in the receipt; set your own when attaching files. After an uncertain result, resend with that ID."
  2. Changed1 schema field changedv0.4.29
    • changedInput schema / properties / operations / description
      Previous value: -"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id?, due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?, attach_uploads?}} · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites quotation must match the cited text exactly, or quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}} · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written."New value: +"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id? (me or an ID), due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?, reservation?, attach_uploads?}}; reservation occupied starts; occupied:G guards any edit; vacant:G releases; replace:G takes over (a reviewer, with a reason, when a person asks) · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites link also takes target_revision, selector, relation and quotation: the exact text, else quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}}; a board post adds link.create related_to from its $ref to the item · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written."
  3. Changed2 schema fields changedv0.4.16
    • changedInput schema / properties / operations / description
      Previous value: -"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id?, due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?}} · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites quotation must match the cited text exactly, or quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?}} · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears."New value: +"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id?, due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?, uploads?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?, attach_uploads?}} · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites quotation must match the cited text exactly, or quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?, uploads?}} · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears. uploads/attach_uploads: upload IDs or absolute local file paths, stored first; if one fails nothing is written."
    • changedInput schema / properties / request_id / description
      Previous value: -"Optional; generated and named in the receipt. After an uncertain result, resend with that ID."New value: +"Optional; named in the receipt; set your own when attaching files. After an uncertain result, resend with that ID."
  4. Changed1 schema field changedv0.4.15
    • changedInput schema / properties / operations / description
      Previous value: -"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id?, due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?}} · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites or relies_on, from/to may be $ref of a new item; a cites quotation must match the cited text exactly, or quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears."New value: +"1-32 of: {op:item.create, ref?, data:{title, body?, work?:{owner_id?, due_at?, criteria?:[{text}]}, context?:{level, state?, steward_id?, open?}, fields?}, allow_duplicate_of?} · {op:item.edit, id, patch:{title?, body?, work?, fields?}} · {op:link.create, data:{type, from, to}}, type related_to, contributes_to, requires, cites, relies_on or works_at (a person record to a company record), from/to may be $ref of a new item; a cites quotation must match the cited text exactly, or quotation_mismatch · {op:link.remove, id} · {op:item.archive, id} · {op:item.restore, id} · {op:message.send, ref?, data:{body, title?, to?:[principal], reply_to?}} · {op:message.acknowledge, messages:[ID]}. work makes an item work, context makes it context (level organization or initiative); fields maps a field to an option, null clears."
  5. First observedv0.4.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare mutability, idempotency and non-destructiveness, so the bar is lower, yet the description adds genuine behavior: atomicity of the whole batch, the basis_changed outcome for stale revisions, and the review-to-propose escalation path. It does not explain what a receipt contains or what happens on partial validation failure, but the core behavioral model is disclosed.

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?

Three short sentences, purpose front-loaded, no filler. It is dense with unexplained domain shorthand ("rN", "basis_changed", "linked-from item") that costs a first-time reader, but nothing is wasted.

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?

For a 7-parameter, nested-object, no-output-schema batch mutation tool, the description covers the concurrency contract and the propose policy but leaves response shape, failure modes, and several parameters to the schema. The unusually detailed operations schema carries much of the burden, so this is adequate but not complete.

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?

Coverage is 57%, and the description meaningfully deepens `expect` beyond the schema's bare `{"<ID>": <revision you read>}` by specifying which items must appear and what happens when a revision is missing. It also ties `reason` to the propose path. But `mode`, `format`, and `workspace_id` get no treatment, leaving the compensation for the coverage gap incomplete.

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?

"Change items and links atomically" gives a verb and resource, and "atomically" usefully distinguishes it as a batch mutation tool. However, it omits major capabilities the schema reveals (item.create, item.archive/restore, message.send/acknowledge), so the stated purpose understates the tool's scope. No explicit contrast with the read-oriented siblings (wirk_query, wirk_show).

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 clause "Context changes apply when you may make them; requires_review means propose with a reason" gives a real conditional for choosing the propose mode. Beyond that, there is no guidance on when to use this tool versus wirk_review or wirk_query, and the apply-vs-propose choice is only implied for one case.

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

Deploy Server

Other Tools