Skip to main content
Glama
Sign In
Council Blackboard

Council Blackboard

by aetheris-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Blackboard Get State

blackboard_get_state

Retrieve the current shared state from the Council Blackboard to synchronize team collaboration and review stored information.

Instructions

Retrieve the shared Council Blackboard state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blackboard_get_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The verb 'retrieve' strongly indicates a non-mutating read operation, and no contrary behaviors are suggested. However, it does not explicitly state that it is side-effect-free or mention any permissions or rate limits.

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, direct sentence with no unnecessary words, making it highly concise.

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?

While the getter nature is clear, the presence of an optional 'mode' parameter with no contextual explanation creates ambiguity about how the state retrieval is scoped, and the output is not described beyond an existing schema.

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

Parameters1/5

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

The only parameter 'mode' has an enum in the schema but no description. The tool description does not explain what filtering or behavior 'mode' controls, leaving its meaning entirely unexplained.

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 retrieves the shared Council Blackboard state, distinguishing it from sibling tools that add, propose, approve, or set modes.

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

Usage Guidelines3/5

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

Usage is implied as a read operation for the blackboard state, but no explicit guidance is given on when to prefer this over alternatives like blackboard_set_mode or colloquium_get_session.

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