Skip to main content
Glama
wirkspace

wirk-mcp

Official
by wirkspace
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wirk_query

Read-onlyIdempotent

Fetch items by ID, title, field filter, meaning-based topic, or receipt, and list what matters for coordination work. Maps bare refs to fetches, known keys to arguments, and other KEY=VALUE pairs to filters.

Instructions

Fetch by ID, short ID or exact title; list with fields; find what matters for about (by meaning on Pro); or look up a receipt. A result "label: query …" maps bare refs to fetch, known keys to arguments, other KEY=VALUE to fields (comma values as lists, except text, linked and folder).

Input Schema

NameRequiredDescriptionDefault
sortNosort=changed is newest first; leading - reverses
waitNoWith inbox=me: hold up to this many seconds (0–60) for a message.
aboutNoWords; on Pro, items ranked by meaning; otherwise items containing every word.
depthNo
fetchNoRefs: ID, short ID, exact title, ID@N, or {ref, revision, select}; a file's derived text: {"fetch":[{"ref":"ID","select":[{"type":"whole","part":{"type":"file","file_id":"F"}}]}]}
limitNo
cursorNo
fieldsNoFilters, e.g. {"status": ["open"], "kind": "work", "owner": "me", "linked": "ID", "changed_days": 7}; text: a case-insensitive substring; kind: work, context, folder, record, message; inbox=me: your unseen messages; participant=[ID]: by or to; state is an initiative's; proposal=["proposed"] lists proposals.
formatNo
receiptNoA request_id: its stored write or review receipt.
max_bytesNo1024–65536; default set by depth
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.29
    • changedInput schema / properties / fields / description
      Previous value: -"Filters, e.g. {\"status\": [\"open\"], \"kind\": \"work\", \"owner\": \"me\", \"linked\": \"ID\", \"changed_days\": 7}; kind: work, context, folder, record, message; inbox=me: your unseen messages; participant=[ID]: by or to; state is an initiative's; proposal=[\"proposed\"] lists proposals."New value: +"Filters, e.g. {\"status\": [\"open\"], \"kind\": \"work\", \"owner\": \"me\", \"linked\": \"ID\", \"changed_days\": 7}; text: a case-insensitive substring; kind: work, context, folder, record, message; inbox=me: your unseen messages; participant=[ID]: by or to; state is an initiative's; proposal=[\"proposed\"] lists proposals."
  2. Changed8 schema fields changedv0.4.15
    • changedInput schema / properties / about / description
      Previous value: -"Words; items ranked by meaning, or containing every word when ranking is unavailable."New value: +"Words; on Pro, items ranked by meaning; otherwise items containing every word."
    • changedInput schema / properties / fetch / description
      Previous value: -"Refs: ID, short ID, exact title, or ID@N for revision N."New value: +"Refs: ID, short ID, exact title, ID@N, or {ref, revision, select}; a file's derived text: {\"fetch\":[{\"ref\":\"ID\",\"select\":[{\"type\":\"whole\",\"part\":{\"type\":\"file\",\"file_id\":\"F\"}}]}]}"
    • addedInput schema / properties / fetch / items / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "object"
+  }
+]
    • removedInput schema / properties / fetch / items / type
      Removed value: -"string"
    • changedInput schema / properties / fields / description
      Previous value: -"Filters, e.g. {\"status\": [\"open\", \"in_progress\"], \"kind\": \"work\", \"owner\": \"me\", \"text\": \"exact words\", \"linked\": \"ID\", \"changed_days\": 7}; kind is work, context, folder or doc; state is an initiative's; proposal=[\"proposed\"] lists proposals."New value: +"Filters, e.g. {\"status\": [\"open\"], \"kind\": \"work\", \"owner\": \"me\", \"linked\": \"ID\", \"changed_days\": 7}; kind: work, context, folder, record, message; inbox=me: your unseen messages; participant=[ID]: by or to; state is an initiative's; proposal=[\"proposed\"] lists proposals."
    • addedInput schema / properties / max_bytes / description
      Added value: +"1024–65536; default set by depth"
    • addedInput schema / properties / sort / description
      Added value: +"sort=changed is newest first; leading - reverses"
    • addedInput schema / properties / wait
      Added value: +{
+  "description": "With inbox=me: hold up to this many seconds (0–60) for a message.",
+  "type": "integer"
+}
  3. First observedv0.4.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description's second sentence adds genuinely non-obvious behavior about how a 'label: query …' result maps bare refs and KEY=VALUE pairs, but it says nothing about pagination (cursor/limit), what depth controls, or response size shaping beyond what the schema states.

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?

Only two sentences and no filler, with the mode list front-loaded. However the second sentence is a dense run-on about result-label parsing that forces re-reading, and the mode enumeration is packed into a semicolon chain rather than structured.

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?

For a 12-parameter, five-mode, nested-object tool with no output schema, the description covers the ref/query grammar but omits paging, depth semantics, format selection, and how the modes interact with limit/cursor. An agent can pick a mode but cannot confidently call it correctly in the list/pagination path.

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 58%, so the schema already documents sort, wait, about, fetch, fields, receipt and max_bytes. The description adds the KEY=VALUE-to-fields mapping rule and the comma-as-list exception for text/linked/folder, which is real added meaning, but it leaves depth, limit, cursor, format and workspace_id entirely unaddressed in both places.

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 description enumerates four modes (fetch by ref, list with fields, meaning search via about, receipt lookup), which goes beyond a tautology, but the phrasing is heavily compressed ('find what matters for about') and never names or distinguishes the siblings wirk_show or wirk_review, which plausibly overlap on reading records by ID.

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?

The only conditional offered is '(by meaning on Pro)' for the about mode. There is no statement of when to use this versus wirk_show or wirk_write, no prerequisites, and no exclusions; an agent must infer mode selection entirely from parameter names.

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