Skip to main content
Glama
Gonzih

nexus-convergence-mcp

by Gonzih

converge_query

Send a query to multiple LLMs simultaneously, perform consensus validation, and receive a structured result with agreement metrics and provenance.

Instructions

Fan out a query to multiple LLMs in parallel (OpenAI, Claude, Gemini, Ollama), run multi-stage consensus validation, and return a structured result with agreement score, truth stability classification, and provenance. NEVER rely on one model answer. Friction between disagreements = intelligence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe query to fan out to multiple models
modelsNoList of model names to query. E.g. ["gpt-4o", "claude-3-5-sonnet-20241022", "gemini-1.5-pro"]. Leave empty for defaults.
policy_setNoOptional policy set identifier for compliance filtering (e.g. "hipaa", "eu-ai-act")

Implementation Reference

  • The tool 'converge_query' handler in the CallToolRequestSchema handler. It validates inputs with Zod schema, calls convergeQuery from client.ts, and returns the JSON result.
    case 'converge_query': {
      const schema = z.object({
        query: z.string().min(1),
        models: z.array(z.string()).default([]),
        policy_set: z.string().optional(),
      });
      const params = schema.parse(args);
      const result = await convergeQuery(params.query, params.models, params.policy_set);
    
      return {
        content: [
          {
            type: 'text' as const,
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:59-85 (registration)
    Tool registration for 'converge_query' with name, description, and input schema (query, models, policy_set) as part of ListToolsRequestSchema.
      name: 'converge_query',
      description:
        'Fan out a query to multiple LLMs in parallel (OpenAI, Claude, Gemini, Ollama), run multi-stage consensus validation, and return a structured result with agreement score, truth stability classification, and provenance. ' +
        'NEVER rely on one model answer. Friction between disagreements = intelligence.',
      inputSchema: {
        type: 'object' as const,
        required: ['query'],
        properties: {
          query: {
            type: 'string',
            description: 'The query to fan out to multiple models',
          },
          models: {
            type: 'array',
            items: { type: 'string' },
            description:
              'List of model names to query. E.g. ["gpt-4o", "claude-3-5-sonnet-20241022", "gemini-1.5-pro"]. Leave empty for defaults.',
            default: [],
          },
          policy_set: {
            type: 'string',
            description:
              'Optional policy set identifier for compliance filtering (e.g. "hipaa", "eu-ai-act")',
          },
        },
      },
    },
  • The convergeQuery function implementation - an HTTP client that POSTs query, models, and policy_set to the convergence service endpoint and returns a ConvergeResult.
    export async function convergeQuery(
      query: string,
      models: string[],
      policySet?: string
    ): Promise<ConvergeResult> {
      return post<ConvergeResult>(`${CONVERGENCE_SERVICE_URL}/converge`, {
        query,
        models,
        policy_set: policySet,
      });
    }
  • The ConvergeResult interface defining the return type of convergeQuery: run_id, status, query, models_used, consensus, final_answer, etc.
    export interface ConvergeResult {
      run_id: string;
      status: string;
      query: string;
      models_used: Array<{ model: string; provider: string; latency_ms: number; error?: string }>;
      successful_models: number;
      failed_models: number;
      consensus: {
        analysis_id: string;
        agreement_score: number;
        stability: string;
        agreed_claims: string[];
        disputed_claims: string[];
        inversion_count: number;
      } | null;
      final_answer: string;
      evidence_ladder_url: string;
    }
  • Zod input validation schema for converge_query: query (required string), models (optional array of strings, default []), policy_set (optional string).
    const schema = z.object({
      query: z.string().min(1),
      models: z.array(z.string()).default([]),
      policy_set: z.string().optional(),
    });
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the parallel fan-out and multi-stage consensus validation, but does not disclose potential costs, rate limits, failure handling (e.g., if a model times out), or the fact that it may be slower than single-model queries. The output format is partially described, but behavioral traits like destructive or read-only are not clarified. The description is adequate but not exhaustive.

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 a single sentence that efficiently conveys the core purpose, process, and output. It uses imperative language ('NEVER rely') to emphasize proper usage. Every phrase serves a purpose, with no redundancy or filler. It is appropriately sized for the tool's complexity.

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 has 3 parameters, no output schema, and no annotations, the description covers the main aspects: what it does, how it works (parallel fan-out, consensus validation), and what it returns (agreement score, truth stability, provenance). It does not explain error behavior or performance trade-offs, but for a tool of this complexity, it is largely complete and leaves minimal ambiguity.

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 description coverage is 100%, so baseline is 3. The description adds minimal extra value: for 'models' it notes 'Leave empty for defaults' which is partly in schema (default value), and for 'policy_set' it provides examples ('hipaa', 'eu-ai-act'). However, it does not explain the significance of the default models or the behavior when a model is unavailable. Overall, it adds only slight incremental meaning 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?

Description clearly states the tool fans out a query to multiple LLMs in parallel, runs multi-stage consensus validation, and returns a structured result with agreement score, truth stability, and provenance. It uses a specific verb ('fan out') and identifies the resource (multiple LLMs). It distinguishes from siblings like check_compliance or list_model_disagreements by focusing on consensus across models.

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

Usage Guidelines4/5

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

The description provides strong usage guidance: 'NEVER rely on one model answer' and 'Friction between disagreements = intelligence' explicitly indicate when to use this tool (when multi-model consensus is needed). However, it does not mention when not to use it or suggest alternatives (e.g., if speed is critical, use a single model), which would elevate it to a 5.

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/Gonzih/nexus-convergence-mcp'

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