Skip to main content
Glama
Sign In
Council Blackboard

Council Blackboard

by aetheris-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Colloquium Commit To Blackboard

colloquium_commit_to_blackboard

Commit a distilled colloquium outcome to the shared blackboard for team access.

Instructions

Commit a distilled colloquium outcome into the shared 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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "colloquium_commit_to_blackboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
typeNoconcept
titleYes
contentYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose side effects, permissions, or return behavior. 'Commit' implies a write operation but without explicit details, the agent cannot anticipate its impact on the blackboard or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it omits critical information. It is under-specified and does not front-load the most important details about the tool's functionality, making it less useful despite its brevity.

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

Completeness1/5

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

Given no annotations and no parameter details, the description is severely incomplete. It lacks information about the tool's integration with the blackboard system, expected inputs, outputs, and its relationship to sibling tools, leaving major gaps for the agent.

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 schema has no per-parameter descriptions, and the description fails to explain the meaning of 'title', 'content', 'tags', or 'type'. The enum values for 'type' are not documented, leaving the agent without any semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'commit' is vague and does not specify the exact operation (add, update, replace) on the blackboard. It mentions 'distilled colloquium outcome' but fails to distinguish this from sibling tools like blackboard_add_item or blackboard_propose_input, leaving the purpose ambiguous.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus siblings. No mention of prerequisites, typical scenarios, or when to avoid it. The description offers no context for selection.

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