Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Run Council

run_council

Submit a question or decision to Meta Council. A panel of specialized AI agents will independently analyze it, then a synthesis step combines their opinions into a unified recommendation with full transparency. Starts asynchronously by default; use get_session with the returned session id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel to use (e.g., 'claude-sonnet-4-6', 'gpt-4o', 'deepseek-chat'). Omit to use user's default.
panelNoPanel slug to use (e.g., 'default', 'technology', 'healthcare'). Use 'auto' for automatic panel selection. Omit to use default panel.
queryYesThe question or decision to analyze
wait_secondsNoOptional synchronous wait (0-90 seconds). Default 0 returns the session id immediately, avoiding reverse-proxy timeouts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate non-read-only, non-idempotent, and non-destructive behavior. The description adds the async-by-default behavior and the need to follow up with get_session, which are not present in annotations. This is meaningful behavioral context that helps the agent invoke and monitor the tool correctly.

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?

Three sentences, each carrying distinct information: purpose, process, and async follow-up. The first sentence front-loads the primary action, and there is no redundant or filler content. Every sentence earns its place.

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

Completeness4/5

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

For a tool with no output schema and four well-documented parameters, the description covers the key behavioral aspect (async session) and points to get_session for result retrieval. It could elaborate on what a completed session looks like, but the follow-up instruction mitigates that gap. Sibling tools like list_panels and recommend_panel are discoverable from the surrounding context.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description indirectly references wait_seconds via 'Starts asynchronously by default,' but it adds no parameter-specific guidance beyond what the schema already provides. The schema handles parameter documentation adequately.

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 starts with 'Submit a question or decision to Meta Council,' naming a specific verb and resource. It distinguishes this from siblings like submit_meta_council_feedback by framing it as a question/decision analysis rather than feedback, and the process description (independent analysis + synthesis) makes its unique role clear.

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 the tool is for submitting analytical questions/decisions and explicitly tells the agent to use get_session with the returned session id for follow-up. However, it never states when not to use this tool or mentions alternatives like recommend_panel or submit_meta_council_feedback, leaving usage selection partly to inference.

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

All Meta Council toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources