Council Blackboard

Blackboard Set Mode

blackboard_set_mode

Switch the Council Blackboard to a chosen operating mode—brainstorming, project creation, story writing, or coding embodiment—to align multi-agent collaboration and state management.

Instructions

Switch the operating mode of the Council Blackboard.

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": {
      "mode": "<mode>"
    },
    "name": "blackboard_set_mode"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

C2.8/5.0

Behavior2/5

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

There are no annotations and no mention of side effects, persistence, permissions, or returned results. The description implies a state change, but does not disclose what changing the mode affects (e.g., pending items, approvals, subsequent tool behavior).

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 a single, clear sentence with no filler or redundant wording.

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

Completeness2/5

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

The tool is relatively simple, but with no annotations, no parameter descriptions, and no explanation of output or effects, the description is not enough to fully understand the tool's behavior in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required enum parameter with values that are somewhat self-explanatory, but schema description coverage is 0% and the description does not explain what each mode means. It adds no additional meaning beyond the bare enum names.

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?

The description clearly states the tool's action ('Switch') and target ('operating mode of the Council Blackboard'), and it is distinct from sibling tools like blackboard_get_state or blackboard_add_item. However, it does not elaborate on what 'operating mode' concretely affects.

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 gives no guidance on when to switch modes versus using other blackboard tools, nor does it explain which mode should be chosen for a given situation. It only states the action, leaving the usage context implicit.

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

Deploy Server