Skip to main content
Glama
Sign In
model-council-mcp-codex

model-council-mcp-codex

by tsarihan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

setup_council

Configure subscription tiers for cloud and local AI providers to control availability and concurrency, then automatically re-detect all usable models and populate the council.

Instructions

Set subscription tiers, then re-detect and auto-populate the council with everything usable. Tiers gate cloud availability and per-provider concurrency: chatgpt (free|plus|pro5x|pro20x), claude (free|pro|max5x|max20x), grok (free|supergrok|premiumplus|heavy), ollama (free|pro|max). Choices persist across reloads. Note: registering a NEW subscription provider or changing concurrency takes full effect after a reload.

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

Input Schema

NameRequiredDescriptionDefault
grokNoGrok (X.AI subscription CLI) tier.
claudeNoClaude subscription tier.
ollamaNoOllama subscription tier.
chatgptNoChatGPT subscription tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.80

TDQS

A3.9/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false, so mutation is known. The description adds valuable behavioral context: 'Choices persist across reloads' and 'registering a NEW subscription provider or changing concurrency takes full effect after a reload.' This discloses persistence and side-effect timing beyond what the annotation conveys.

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 and front-loaded: a clear action sentence, a brief contextual explanation, and an important caveat. Every sentence earns its place with no fluff or redundancy.

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 there is no output schema, the description adequately covers the tool's behavior, side effects, and persistence. It doesn't describe return values, but that may be covered by siblings like 'get_council_config'. The reload note addresses a critical operational detail, making it sufficiently complete for a setup tool.

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?

Schema coverage is 100% with each parameter described and enum values provided. The description adds semantic meaning by explaining that 'Tiers gate cloud availability and per-provider concurrency,' which is not in the schema. It repeats enum lists but ties them to the higher-level purpose.

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 clearly states the verb+resource: 'Set subscription tiers, then re-detect and auto-populate the council.' It also specifies the exact tiers for each provider, giving strong scope. However, it does not explicitly distinguish itself from the sibling 'configure_council', which could be confused for similar functionality.

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 context implies this is for initial setup ('Set subscription tiers, then re-detect and auto-populate'), and the note about persistence and reload provides situational guidance. However, it does not explicitly state when to use this vs alternatives like 'configure_council', nor does it specify exclusions or prerequisites.

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