Council Blackboard

Colloquium Interject

colloquium_interject

Insert a high-priority supervisor directive into the colloquium stream to steer agent deliberations.

Instructions

Insert a high-priority supervisor directive into the colloquium stream.

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": {
      "directive": "<directive>"
    },
    "name": "colloquium_interject"
  }
}

Input Schema

Name	Required	Description	Default
`directive`	Yes
`sender_name`	No		Supervisor (HITL)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description bears the full burden of disclosing behavior. It indicates an insertion action but does not mention side effects, ordering, persistence, visibility, permissions, idempotency, or return 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, focused sentence with no redundant words or unnecessary structure.

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 tool is simple, but the description omits practical context such as output, error cases, or effects on the stream. It covers the basic purpose but not enough for confident use in varied situations.

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 description does not meaningfully explain the parameters. It indirectly references 'directive' but not 'sender_name', and there are no per-parameter descriptions in the schema to compensate.

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 states a specific verb ('Insert'), a clear object ('high-priority supervisor directive'), and the target resource ('colloquium stream'). It clearly distinguishes this tool's purpose from the sibling colloquium tools.

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?

The phrase 'high-priority supervisor directive' implies when the tool should be used, but it does not explicitly state when to prefer this over alternatives or when not to use it.

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

Deploy Server