Skip to main content
Glama
Sign In
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_task

Creates a workspace-scoped, idempotent task record for multi-agent coordination, including sender, recipient, subject, body, priority, parent, and branch metadata.

Instructions

Create a TASK using Core T1 and its workspace-scoped operation identity. Repeated requests retain Core idempotency semantics.

Input Schema

NameRequiredDescriptionDefault
bodyYes
parentNo
senderYes
subjectYes
priorityNoP2
branch_ofNo
recipientYes
referencesNo
risk_levelNo
thread_keyNo
operation_idYes
workspace_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changedv4.0.5
    • removedInput schema / properties / body / description
      Removed value: -"Task body in Markdown."
    • addedInput schema / properties / branch_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / operation_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / parent
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / priority / description
      Removed value: -"``P0`` / ``P1`` / ``P2`` / ``P3`` (or legacy aliases).\n        Default: ``P2``."
    • removedInput schema / properties / recipient / description
      Removed value: -"Recipient role code (uppercase). May use the slot\n        form ``ROLE.D1`` or ``TEAM`` for broadcast."
    • addedInput schema / properties / references / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / references / default
      Previous value: -""New value: +null
    • removedInput schema / properties / references / description
      Removed value: -"Comma-separated task filenames for ``references:`` field."
    • removedInput schema / properties / references / type
      Removed value: -"string"
    • addedInput schema / properties / risk_level / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / risk_level / default
      Previous value: -""New value: +null
    • removedInput schema / properties / risk_level / description
      Removed value: -"``low`` / ``medium`` / ``high`` / ``irreversible``.\n        Leave empty to accept the default (``medium``)."
    • removedInput schema / properties / risk_level / type
      Removed value: -"string"
    • removedInput schema / properties / sender / description
      Removed value: -"Sender role code (uppercase)."
    • removedInput schema / properties / subject / description
      Removed value: -"One-line subject for the ``subject:`` frontmatter field."
    • addedInput schema / properties / thread_key / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / thread_key / default
      Previous value: -""New value: +null
    • removedInput schema / properties / thread_key / description
      Removed value: -"Optional thread identifier."
    • removedInput schema / properties / thread_key / type
      Removed value: -"string"
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "sender",
-  "recipient",
-  "subject",
-  "body"
-]New value: +[
+  "workspace_id",
+  "operation_id",
+  "sender",
+  "recipient",
+  "subject",
+  "body"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv3.2.4

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints at idempotency ("Repeated requests retain Core idempotency semantics") but never says what that means concretely — does the same operation_id return the same task, or error? Nothing on permissions, side effects, or whether parent/branch_of create implicit relationships.

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?

Two short sentences with no padding, and the action is front-loaded. But the brevity comes at the cost of substance: both sentences are jargon-dense placeholders rather than information an agent can act on.

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?

A 12-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage needs far more than two sentences. Key gaps: relationship semantics for parent/branch_of, valid values for priority/risk_level, and what success returns.

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 coverage is 0% across 12 parameters, so the description must compensate and largely fails. It only gestures at workspace_id scoping and operation_id idempotency, leaving parent, branch_of, thread_key, references, risk_level, and the meaning of priority "P2" completely unexplained.

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 verb+resource ("Create a TASK") is stated, but "Core T1" and "workspace-scoped operation identity" are undefined jargon rather than a description of what a task is or how it differs from siblings like write_issue or write_report, which also appear to create work items.

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?

No indication of when to use create_task versus write_issue, write_report, write_review, or create_branch, all of which sit in the same family of creation tools. No prerequisites, no preconditions (e.g., does the workspace need to be initialized/validated first?).

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