Skip to main content
Glama
BrightbeamAI

@brightbeamai/chap-coordinator-mcp

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

chap.task.create

chap.task.create

Create a task assigned to one participant, optionally requiring a reviewer decision for completion.

Instructions

Create a task: a unit of work assigned to one participant. Set review_required to make the task's completion depend on a reviewer decision rather than on the assignee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesThe delegator. Must be a workspace member.
kindYesTask kind, e.g. 'draft_response' or 'review'. Free text; the coordinator records it without interpreting it.
modeNoMode for this task, defaulting to the workspace mode. A mode above the workspace ceiling is refused with -32040.
inputYesTask-specific input payload.
assigneeYesWho the task is assigned to. Must be a workspace member, and must not be paused: assigning to a paused member is refused with -32063.
deadlineNoWhen the task is due, as an ISO 8601 timestamp. Recorded on the task; the coordinator does not act on it.
workspaceYesWorkspace identifier, e.g. 'wsp_techcorp_support'.
routing_hintsNoSignals recorded on the task and read by the routing/1.0 methods: task.route, review.depth and escalate.auto. Recording a hint has no effect on its own; it is consulted only when one of those methods is called.
idempotency_keyNoCaller-chosen key for safe retries. A second create carrying a key already seen in this workspace returns the original task and records nothing further. The workspace retains the 10,000 most recent keys.
review_requiredNoWhen true, chap.task.complete opens a review instead of completing: the output becomes the artefact under review, and the task reaches 'completed' only on a reviewer decision. chap.task.update cannot complete such a task. Under modes/1.0 a trial-mode task has this set to true whatever is passed here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.13

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose one meaningful trait: setting review_required makes completion depend on a reviewer decision rather than on the assignee. However, it does not mention idempotency-key retention, mode-ceiling refusals, or what happens after creation, so transparency is only partial.

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

Conciseness5/5

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

Two sentences, with the core action front-loaded and the second sentence reserved for the most important behavioral switch. There is no filler or redundancy, and every sentence earns its place.

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

Completeness3/5

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

The input schema is unusually rich and compensates for the terse description, but there is no output schema and no annotations. The definition still lacks a high-level statement of the task lifecycle, return value, and side effects such as idempotent retries, making it adequate but not fully complete for a 10-parameter creation tool.

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%, so the baseline of 3 applies. The description's review_required sentence restates a simplified version of the schema's detailed behavior without adding new semantic information beyond what the schema already provides.

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

Purpose5/5

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

The description clearly states the operation with a specific verb and resource: 'Create a task: a unit of work assigned to one participant.' This makes it easy to distinguish from lifecycle siblings like chap.task.update and chap.task.complete, whose verbs indicate different stages.

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 description does not state when to choose this tool over alternatives such as chap.task.update or chap.task.complete, and it offers no when-not-to-use guidance. The only guidance is the review_required parameter advice, which concerns a single option rather than tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools