Skip to main content
Glama
Sign In
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_tasks

Retrieve validated TASK records and filter by stage, parent, sender, recipient, or branch to inspect tasks and their relations in multi-agent coordination.

Instructions

List validated canonical TASK facts, optionally filtered by stage or relations.

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
offsetNo
parentNo
senderNo
branch_ofNo
recipientNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv4.0.5
    • addedInput schema / properties / branch_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / date
      Removed value: -{
-  "default": "",
-  "description": "Filter by YYYYMMDD date stamp.",
-  "type": "string"
-}
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / limit / default
      Previous value: -0New value: +null
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of rows to return (0 = no limit)."
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
    • removedInput schema / properties / offset / description
      Removed value: -"Number of rows to skip before returning."
    • addedInput schema / properties / parent
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / recipient / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / recipient / default
      Previous value: -""New value: +null
    • removedInput schema / properties / recipient / description
      Removed value: -"Filter by recipient role code. Matches ``to-ROLE``,\n``to-ROLE.SLOT``, and ``to-TEAM`` broadcasts."
    • removedInput schema / properties / recipient / type
      Removed value: -"string"
    • addedInput schema / properties / sender / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / sender / default
      Previous value: -""New value: +null
    • removedInput schema / properties / sender / description
      Removed value: -"Filter by sender role code (case-insensitive)."
    • removedInput schema / properties / sender / type
      Removed value: -"string"
    • addedInput schema / properties / stage
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / status
      Removed value: -{
-  "default": "open",
-  "description": "``open`` (default), ``archived``, or ``all``.",
-  "type": "string"
-}
    • 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.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation but does not disclose pagination behavior, default ordering, authentication/permission requirements, or what a 'validated canonical' fact means in practice, leaving significant behavioral gaps.

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?

The single sentence is front-loaded and free of filler, but it is under-specified rather than appropriately concise. It earns its place as a summary but omits information the agent needs.

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?

With no annotations, no output schema, and seven parameters at 0% schema coverage, the one-sentence description is not complete enough. An agent lacks guidance on filtering semantics, pagination, ordering, and result shape.

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 description coverage is 0%, so the description must compensate for all seven parameters. It mentions only 'stage' and vaguely references 'relations,' leaving limit, offset, parent, sender, branch_of, and recipient completely unexplained in both schema and description.

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 ('List') and resource ('canonical TASK facts'), so an agent knows this is a read/list operation over tasks. It does not distinguish itself from sibling list tools like list_reports or list_issues beyond the resource name, leaving some ambiguity.

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?

Only says results can be 'optionally filtered by stage or relations,' which is a capability statement rather than guidance on when to choose this tool over list_reports/list_issues or inspect_task/read_task. No exclusions, prerequisites, or alternatives are named.

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