Skip to main content
Glama

omnarai-mcp

by io.github.justjlee

omnarai_council

Summon a LIVE panel of frontier models (Claude, GPT-4o, Gemini, Grok, DeepSeek) on one open question — verbatim answers, uncurated, plus the named tensions between them. Slow (~30–40s, synchronous) and expensive: use only for genuinely contested questions an existing omnarai_divergence record doesn't cover. Every run mints a new divergence record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe open question for the live panel, phrased as you would to a human expert.

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: synchronous execution taking 30-40s, high cost, and the side effect of minting a new divergence record. It also describes outputs as uncurated with named tensions.

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, well-structured sentence that front-loads the core action and packs essential details (models, output nature, timing, cost, alternative) without waste.

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

Completeness5/5

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

Given no output schema and no annotations, the description fully explains what the tool returns (verbatim answers, tensions) and key behavioral context (speed, cost, side effects). It is complete for a single-parameter 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?

The schema already covers the single parameter with a clear description. The tool description adds a useful nuance about phrasing the question 'as you would to a human expert', enhancing semantic clarity 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?

The description explicitly states the tool summons a live panel of specific frontier models for one open question, providing verbatim answers and tensions. It distinguishes from siblings by mentioning existing omnarai_divergence records as an alternative.

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?

The description clearly specifies when to use: only for genuinely contested questions not covered by an existing divergence record. It also warns against using unnecessarily due to slowness and expense, providing strong guidance.

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

All omnarai-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: context for bounded retrieval, council for live panel, divergence for reading existing records, info for meta-data, inquiry_brief for converting drafts, job for polling async tasks, query for async queries, and trace for counterfactual analysis. No overlap.

Naming Consistency5/5

All tools follow a consistent 'omnarai_<noun>' pattern in snake_case (context, council, divergence, info, inquiry_brief, job, query, trace). No mixed styles or irregular verbs.

Tool Count5/5

8 tools is well-scoped for a knowledge retrieval and deliberation system. It covers retrieval, live panel, divergence records, meta-info, inbox brief generation, async job polling, query execution, and tracing without unnecessary redundancy.

Completeness4/5

The tool surface covers core workflows: retrieval, deliberation, async job management, and meta-information. The only minor gap is the absence of tools for modifying or updating corpus data, but this aligns with the server's apparent read-only nature. Comprehensive for its stated purpose.

Resources