Skip to main content
Glama

council

Sends the same message to several web chat sites in parallel and returns each answer separately, helping compare perspectives for decisions that need several opinions.

Instructions

The same message to several web chats in parallel (default glm, qwen, deepseek); each answer separately, each cut to max_chars like ask (full text in answer_file). Costs one ask per site: use it for decisions worth several opinions, not for routine questions.

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

Input Schema

NameRequiredDescriptionDefault
filesNo
sitesNo
threadNo
messageNo
new_chatNo
max_charsNo
message_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers the key traits: parallel fan-out, per-site cost accounting, truncation to max_chars, and full text persisted in answer_file. It does not say what happens if one site fails or what permissions/config the sites need, which keeps it short of a 5.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action, then cost/usage caveats. The parenthetical default list is useful rather than filler, though the 'each answer separately, each cut to max_chars' clause is slightly compressed to the point of awkwardness.

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?

It covers the output side well (per-site answers, answer_file, truncation) despite having no output schema and no annotations. However, for a 7-parameter tool with zero schema descriptions and zero required fields, leaving five parameters unaddressed is a real gap an agent must guess through.

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 7 parameters, so the description must compensate, but it only clarifies max_chars (truncation, same as ask) and hints at sites defaults. message, files, thread, message_file, and new_chat are left entirely unexplained beyond their bare names and types.

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 and resource — sends the same message to several web chats in parallel — and names the defaults (glm, qwen, deepseek). It implicitly contrasts with the sibling 'ask' by noting each answer is handled separately and truncated 'like ask', so an agent can distinguish the multi-site fan-out from a single-site query.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('decisions worth several opinions') and when-not ('not for routine questions'), plus the concrete cost rule of one ask per site. That is a complete routing rule an agent can act on without inference.

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