Skip to main content
Glama

conclave_config

View current Conclave MCP configuration including member models, chairman rotation, consensus thresholds, and API key status to monitor AI consultation settings.

Instructions

View current conclave configuration.

Shows conclave member models, current chairman with rotation info, available chairman presets, consensus thresholds, and API key status.

Also shows custom conclave selection if active.

Returns: Current configuration as formatted JSON

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The conclave_config tool handler function. It retrieves and formats the current conclave configuration including API key status, active conclave (custom or tier-based), chairman rotation info, consensus thresholds, and available presets. Returns formatted JSON output.
    @mcp.tool()
    async def conclave_config() -> str:
        """View current conclave configuration.
    
        Shows conclave member models, current chairman with rotation info,
        available chairman presets, consensus thresholds, and API key status.
    
        Also shows custom conclave selection if active.
    
        Returns:
            Current configuration as formatted JSON
        """
        rotation_info = get_rotation_info()
    
        # Check for custom conclave
        custom_models, custom_chairman, source = get_active_models()
    
        if source == "custom":
            size_validation = validate_council_size(custom_models, custom_chairman)
            active_config = {
                "mode": "custom",
                "chairman": custom_chairman,
                "members": custom_models,
                "size": {
                    "total_members": size_validation["total_size"],
                    "is_odd": size_validation["valid"],
                    "status": size_validation["message"],
                },
            }
        else:
            size_validation = validate_council_size()
            active_config = {
                "mode": "tier-based",
                "default_tier": "standard",
                "active_models": COUNCIL_MODELS,
                "size": {
                    "total_members": size_validation["total_size"],
                    "is_odd": size_validation["valid"],
                    "chairman_in_conclave": size_validation["chairman_included"],
                    "status": size_validation["message"],
                },
            }
    
        config = {
            "api_key_configured": bool(OPENROUTER_API_KEY),
            "active_conclave": active_config,
            "tiers": get_tier_info(),
            "chairman": {
                "current": custom_chairman if source == "custom" else rotation_info["current_chairman"],
                "rotation_enabled": rotation_info["rotation_enabled"] if source != "custom" else False,
                "rotation_period_days": rotation_info["rotation_period_days"],
                "days_until_rotation": rotation_info["days_until_rotation"] if source != "custom" else "N/A (custom)",
                "chairman_pool": rotation_info["chairman_pool"],
            },
            "consensus": {
                "strong_threshold": f"{CONSENSUS_STRONG_THRESHOLD:.0%}",
                "moderate_threshold": f"{CONSENSUS_MODERATE_THRESHOLD:.0%}",
                "tiebreaker_enabled": CHAIRMAN_TIEBREAKER_ENABLED,
            },
            "presets": CHAIRMAN_PRESETS,
        }
    
        return f"## Conclave Configuration\n\n```json\n{json.dumps(config, indent=2)}\n```"
  • Helper function used by conclave_config to determine if a custom conclave is active or if the default tier-based configuration should be used.
    def get_active_models() -> tuple[list[str], str | None, str]:
        """
        Get the currently active models and chairman.
    
        Returns:
            (models, chairman, source) where source is "custom" or "tier"
        """
        global _custom_conclave
    
        if _custom_conclave:
            return (
                _custom_conclave["models"],
                _custom_conclave["chairman"],
                "custom"
            )
    
        # Default to standard tier
        return (COUNCIL_STANDARD, None, "tier")
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that this is a read-only operation ('View') and describes the return format ('formatted JSON'), but lacks details on permissions, rate limits, or error behavior. It adds some context about what data is included, which is helpful but not comprehensive.

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 front-loaded with the core purpose, followed by specific details in bullet-like structure, and ends with return information. Every sentence adds value without redundancy, making it efficient and well-organized.

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?

Given the tool's complexity (configuration viewing with multiple data points), no annotations, and an output schema present, the description is mostly complete. It lists what data is shown and the return format, but could improve by mentioning sibling differentiation or behavioral constraints like authentication needs.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description correctly doesn't discuss parameters, earning a high baseline score for not adding unnecessary information.

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 specific action ('View current conclave configuration') and lists the exact resources it shows (member models, chairman info, presets, thresholds, API key status, custom selection). It distinguishes from siblings like 'conclave_estimate' or 'conclave_reset' by focusing on configuration viewing rather than estimation or resetting.

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?

The description provides no guidance on when to use this tool versus alternatives like 'conclave_models' (which might show models only) or 'conclave_full' (unclear purpose). It implies usage for viewing configuration but doesn't specify scenarios, prerequisites, or exclusions.

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/stephenpeters/conclave-mcp'

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