Skip to main content
Glama

delimit_deliberate

Achieve unanimous agreement among multiple AI models through direct deliberation. Models debate or dialogue until consensus is reached, providing reliable answers to complex questions.

Instructions

Run multi-model consensus via real AI-to-AI deliberation (Pro).

Models debate each other directly until unanimous agreement. Free tier: 3 deliberations using Gemini Flash + GPT-4o-mini, no setup required. BYOK: configure your own API keys in ~/.delimit/models.json for unlimited use with any models (Grok, Claude, Gemini Pro, GPT-4o, etc).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe question to reach consensus on.
contextNoBackground context for all models.
modeNo"dialogue" (short turns) or "debate" (long essays).dialogue
max_roundsNoMaximum rounds (default 3 for debate, 6 for dialogue).
save_pathNoOptional file path to save the full transcript.
scopeNoOptional scope override — "strategic", "social", or "operational". When empty, the engine classifies from keywords in the question and context. Strategic and social scopes enforce the 3-model minimum (charter consensus-thresholds) and allow Grok as a tiebreaker on deadlock.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description provides behavioral context: it mentions deliberation process, model configuration, free tier limits, and scope behavior. However, it does not disclose whether the tool has side effects or creates persistent state.

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 concise with no redundant sentences. It packs key details (models, tiers, scope behavior) in a few lines, making it efficient and easy to parse.

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

Completeness5/5

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

Given the output schema exists and the description covers free vs BYOK, scope parameters, and the deliberation mechanism, it is comprehensive for the tool's complexity.

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

Parameters5/5

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

All 6 parameters have schema descriptions (100% coverage), and the description adds significant value by explaining tier differences, BYOK setup, and scope override effects beyond the schema.

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 verb 'Run' and the resource 'multi-model consensus via real AI-to-AI deliberation', which is specific and distinguishes it from other tools on the server.

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 description implies usage for reaching consensus through deliberation and explains free vs BYOK tiers, but does not explicitly mention when not to use this tool or point to alternative siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server