Skip to main content
Glama
Sign In
@brightbeamai/chap-coordinator-mcp

@brightbeamai/chap-coordinator-mcp

Official
by BrightbeamAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Comment on deliberation

chap.deliberate.comment

Record a comment on an open deliberation to preserve the reasoning behind a vote, even though it carries no weight in the outcome.

Instructions

Record a comment on an open deliberation, so the reasoning behind a vote survives alongside the tally. Comments carry no weight in the outcome and may be added by any participant at any point before chap.deliberate.close.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "from": "<from>",
      "deliberation_id": "<deliberation_id>",
      "comment": "<comment>"
    },
    "name": "chap.deliberate.comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesParticipant URI, e.g. 'human:alice@example.org' or 'agent:bot@local'.
commentYesThe contribution to record. Comments are kept with the deliberation and in the audit log, so the reasoning survives the vote.
workspaceYesWorkspace identifier, e.g. 'wsp_techcorp_support'.
deliberation_idYesIdentifier returned by chap.deliberate.open. A closed deliberation is refused with -32032.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.13

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior; the description adds that comments are weightless in the outcome and admissible only before close, which is real semantic context. The refusal-after-close code lives in the schema rather than here, so it isn't fully self-contained.

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 tight sentences, front-loaded with the action and then the constraint. Every clause earns its place; nothing is repeated from the schema or annotations.

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?

For a four-required-param mutation with no output schema, the description covers purpose, audience, timing, and effect, and the schema carries error codes and parameter detail. Only minor gaps (duplicate-comment behavior given non-idempotency) remain.

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 all four parameters are already documented with examples and the error code for a closed deliberation. The description adds no syntax or format detail beyond the schema, which is the baseline-3 case.

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?

States a specific verb and resource ('Record a comment on an open deliberation') and immediately scopes it against the tally ('carry no weight in the outcome'), so an agent can distinguish it from chap.deliberate.vote and chap.deliberate.close without opening any schema.

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

Usage Guidelines4/5

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

Gives clear conditions: any participant, at any point before chap.deliberate.close. It implicitly separates this from voting (comments have no effect on outcomes), which is useful routing. It does not name an explicit alternative tool or a 'do not use when' case, so it falls short of 5.

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