Skip to main content
Glama
BrightbeamAI

@brightbeamai/chap-coordinator-mcp

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

chap.control.snapshot

chap.control.snapshot

Capture a workspace state as an artefact and receive its ID, enabling a later rollback to that exact point. Select which aspects to include, from members and open tasks to policy and audit.

Instructions

Capture the workspace state as an artefact and return its id, which chap.control.rollback takes as its target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesParticipant URI, e.g. 'human:alice@example.org' or 'agent:bot@local'.
labelNoName for this snapshot, recorded on the artefact. chap.control.rollback identifies a snapshot by its artefact id, not by label.
includeNoWhich aspects of the workspace to capture. Recognised values are 'members', 'open_tasks', 'mode_ceiling', 'policy' and 'audit'. Defaults to members, open_tasks and mode_ceiling.
workspaceYesWorkspace identifier, e.g. 'wsp_techcorp_support'.

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 must carry the behavioral disclosure. It states that a snapshot artefact is created and an id is returned, which covers the primary side effect, but it does not mention permissions, storage implications, or whether the workspace is modified.

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?

A single, concise sentence that conveys the essential purpose and output without redundancy or fluff.

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 description mentions the return value and its use in rollback, which is important, but it omits broader context such as when to snapshot, output format details (beyond 'id'), and any related caveats. Given the simple nature of the tool, this is adequate but not complete.

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?

The input schema provides full field descriptions, including the recognized values for 'include'. The tool description adds no extra parameter meaning, so the baseline score of 3 is appropriate given the high schema coverage.

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?

Clearly states it captures the workspace state as an artefact and returns an id, with the explicit link to chap.control.rollback as the target. This distinguishes it from related control tools and makes its purpose unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives. It only implies a relationship to rollback by noting the returned id is used as a rollback target, but does not state prerequisites or situations where a snapshot is appropriate.

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