Skip to main content
Glama

council_deliberate

Run parallel multi-model deliberation and judge synthesis to answer high-stakes questions, architecture decisions, and debugging strategy while reducing hallucination risk.

Instructions

Run multi-model deliberation: several models answer a question in parallel, then a judge synthesizes the best answer. Use for high-stakes decisions, architecture questions, debugging strategy, or any question where hallucination risk matters.

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": {
      "question": "<question>"
    },
    "name": "council_deliberate"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes
include_rawNo
num_advocatesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the core execution model (parallel answers plus judge synthesis). However, it omits operational characteristics an agent would want before invoking a multi-model fan-out: relative cost, latency, and whether model selection is configurable.

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?

Two tight sentences: the mechanism is front-loaded, then the routing guidance. There is no filler or repetition.

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?

An output schema exists, so return-shape explanation isn't required, and the core purpose is fully covered. The remaining gaps are the undocumented parameters and absent cost/latency expectations for a fan-out call.

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?

Schema description coverage is 0% across all three parameters, so the description must compensate and largely does not. 'Several models' loosely implies num_advocates, but include_raw and num_advocates are never explained, and the format/scope of 'question' is undefined.

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 gives a concrete verb and resource ('Run multi-model deliberation') and, unusually, explains the mechanism: several models answer in parallel then a judge synthesizes. That makes it obvious the tool is distinct from the sibling council_list_models, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It lists concrete when-to-use contexts: high-stakes decisions, architecture questions, debugging strategy, and anything where hallucination risk matters. It stops short of stating when NOT to use it (e.g., trivial factual lookups where the extra latency and cost aren't warranted).

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