Skip to main content
Glama
Sign In
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

archive_task

Request Core T7 archival for a completed task, with Core enforcing authorization and family convergence before archiving.

Instructions

Request Core T7 done to archive; Core enforces authorization and family convergence.

Input Schema

NameRequiredDescriptionDefault
actorYes
task_idYes
review_refNo
profile_refYes
family_digestNo
authorization_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv4.0.5
    • addedInput schema / properties / actor
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / authorization_ref
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / family_digest
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / lang
      Removed value: -{
-  "default": "",
-  "description": "Kept for 0.5.4 parity; currently unused because the\nlibrary does not need locale for this operation.",
-  "type": "string"
-}
    • addedInput schema / properties / profile_ref
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / review_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / task_id / description
      Removed value: -"Task ID (e.g. ``TASK-20260423-001``) or full filename."
    • changedInput schema / required
      Previous value: -[
-  "task_id"
-]New value: +[
+  "task_id",
+  "actor",
+  "authorization_ref",
+  "profile_ref"
+]
    • 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

D1.9/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 discloses that Core enforces authorization and family convergence, but it does not explain what archiving actually does, whether it is reversible, what permissions are required, or what happens to related family/workflow state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence but is cryptic and under-specified rather than efficient. Crucial details are compressed into jargon like 'Core T7 done' that an agent cannot reliably interpret.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex mutation tool with 6 parameters, no annotations, and no output schema. The description does not provide enough information about purpose, preconditions, parameter meanings, or behavior for an agent to invoke it correctly.

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% for 6 parameters, so the description must compensate heavily. It only loosely hints at authorization and family convergence, leaving task_id, actor, profile_ref, and review_ref unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name says archive_task, but the description's phrasing 'Request Core T7 done to archive' is opaque jargon rather than a clear statement that this archives a task. It does not distinguish the operation from sibling task lifecycle tools such as approve_task, reject_task, or submit_task.

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?

There is no explicit guidance on when to use this tool, when not to, or which sibling tools are alternatives. The mention of authorization and family convergence hints at preconditions but does not tell an agent when archiving is appropriate.

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