Skip to main content
Glama
BrightbeamAI

@brightbeamai/chap-coordinator-mcp

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

chap.control.pause

chap.control.pause

Pause a task, stop new assignments to a participant, or freeze a workspace while keeping audit and resume actions available.

Instructions

Pause work. Scoped to a task it moves that task to paused; to a participant it stops new tasks being assigned to them; to the workspace it refuses every method except describing, reading the audit log, joining, leaving and resuming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesParticipant URI, e.g. 'human:alice@example.org' or 'agent:bot@local'.
scopeNoWhat the pause applies to. 'task' moves one task to 'paused'; a task that is completed, declined, cancelled or superseded is refused with -32061. 'participant' stops new tasks being assigned to that member and leaves their existing work running. 'workspace' refuses every method except workspace.create, workspace.describe, control.resume, audit.read, participant.join and participant.leave.task
reasonNoWhy the pause was applied. Recorded in the audit entry.
task_idNoTask identifier returned by chap.task.create.
workspaceYesWorkspace identifier, e.g. 'wsp_techcorp_support'.
participant_uriNoWhose work to pause, when scope is 'participant'. Must be a workspace member.
in_flight_policyNoRecorded with the request, and echoed back when scope is 'participant'. The coordinator does not act on it: under either value, work already under way is left alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.13

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the full burden is on the description. It transparently discloses side effects: moving tasks to paused, stopping new assignments for participants, and restricting workspace methods. It also honestly states in_flight_policy is recorded but ignored, which is important behavioral information.

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?

The description is concise and front-loaded with 'Pause work.' followed by a clear breakdown of the three scopes. It avoids unnecessary detail and is easy to scan.

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

Completeness5/5

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

The description covers all scopes, explains the in_flight_policy behavior, and mentions the workspace method restrictions. Given the tool's complexity and the detailed parameter schema, this is complete enough for an agent to understand when and how to use it.

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 each parameter already has a detailed description. The tool description summarizes the scope parameter but does not add substantive new information beyond what is already in the schema, so the baseline of 3 is appropriate.

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 tool pauses work and explains the three scoped behaviors (task, participant, workspace). It distinguishes from sibling control tools like resume and cancel by specifying exactly what pause does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly defines when to use pause based on scope, and even notes the in_flight_policy is not acted upon, preventing misuse. It implicitly contrasts with resume/cancel by clarifying pause's effects.

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