Skip to main content
Glama
BrightbeamAI

@brightbeamai/chap-coordinator-mcp

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Supersede task

chap.control.supersede
Destructive

Replace a task with a successor in one call: the original becomes superseded and linked, review requirements carry over, and paused assignees are refused.

Instructions

Replace a task with a successor in one call. The original moves to superseded and stays linked to its replacement. The successor requires review when the original did, whatever its own review_required says, and a paused assignee is refused with -32063.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesParticipant URI, e.g. 'human:alice@example.org' or 'agent:bot@local'.
reasonNoWhy the original is being replaced. Recorded in the audit entry.
task_idYesThe task being replaced. It moves to 'superseded' and is linked to the successor rather than deleted.
workspaceYesWorkspace identifier, e.g. 'wsp_techcorp_support'.
successor_taskYesThe replacement task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • changedInput schema / properties / successor_task / properties / assignee / description
      Previous value: -"Who takes the replacement on. Defaults to the superseded task's assignee, and must be a workspace member."New value: +"Who takes the replacement on. Defaults to the superseded task's assignee, and must be a workspace member who is not paused."
    • addedInput schema / properties / successor_task / properties / mode
      Added value: +{
+  "description": "Mode for the successor, defaulting to the superseded task's. A mode above the workspace's current ceiling is refused with -32040.",
+  "enum": [
+    "shadow",
+    "trial",
+    "production"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / successor_task / properties / review_required
      Added value: +{
+  "description": "Whether completing the successor needs a reviewer decision. A successor of a task that requires review requires it whatever is passed here, and under modes/1.0 so does a trial-mode successor.",
+  "type": "boolean"
+}
  2. First observedv0.2.13

TDQS

A3.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=false/idempotent annotations: discloses that the original is superseded-and-linked rather than deleted, that review requirement is inherited from the original regardless of review_required, and the specific error code (-32063) for a paused assignee. Rich behavioral detail for a mutation.

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 tight sentences, front-loaded with purpose then behavior/edge cases. No filler, though the review-inheritance clause is dense and slightly overlaps the schema.

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

Completeness4/5

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

No output schema exists, but annotations cover the safety profile and the description covers the key mutation quirks (non-deletion, review inheritance, error code). Mode-ceiling (-32040) and idempotency are left to schema/annotations, a minor gap.

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 description coverage is 100% and the schema already documents the review inheritance rule and the not-paused assignee constraint. The description adds only the -32063 error code, so it sits at the baseline for a fully documented schema.

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 and resource ('Replace a task with a successor') and clarifies the outcome (original moves to superseded, stays linked). The supersede semantics distinguish it conceptually from chap.task.update/complete/cancel, though no sibling is named explicitly.

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?

Explains what happens during the call but never says when to choose supersede over alternatives like chap.control.cancel, chap.task.update, or chap.task.route. No exclusions or prerequisites for invocation are given.

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