Skip to main content
Glama
Sign In
Council Blackboard

Council Blackboard

by aetheris-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Colloquium Get Session

colloquium_get_session

Inspect the active colloquium session to review its current state and message history.

Instructions

Inspect the current AI-first colloquium session.

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": "colloquium_get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
limit_messagesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The verb 'Inspect' implies a read-only operation, but no explicit side-effect, permission, or safety behavior is disclosed, and there are no annotations to supplement this.

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?

A single clear sentence with no filler or redundant information.

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 description omits parameter semantics and does not clarify expected output or interaction context, which is insufficient even for a simple inspection tool.

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, limit_messages, is not described in the tool description or schema beyond its type and default, leaving its meaning and effect entirely implicit.

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 'Inspect' and a specific resource 'current AI-first colloquium session', clearly distinguishing it from sibling tools like colloquium_interject or colloquium_update_rule_of_motion.

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?

No guidance on when to use this tool versus alternatives; it only describes the target resource without conditions or exclusions.

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