Skip to main content
Glama

omnarai-mcp

by io.github.justjlee

omnarai_divergence

Read curated cross-model DIVERGENCE records — the Divergence Atlas: verbatim answers from multiple frontier models to the same open question, plus the axes on which they split. Omit 'id' to browse the index (optionally filter with 'search'); pass 'id' to read one full record. Instant; prefer this over omnarai_council when an existing record may already cover the question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOptional. A divergence record id (e.g. from the browse index). Returns the full record.
searchNoOptional keyword filter for the browse index. Ignored when 'id' is given.

TDQS

A4.7/5.0
Behavior4/5

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

No annotations, so description handles it. States 'Instant' for speed and describes data structure. Could clarify behavior when both id and search are given (schema says search ignored), but not required.

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?

Concise 4-sentence description, front-loaded with purpose, no filler.

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?

For a read tool with 2 optional params and good schema, description fully covers what tool does, how to use, and when to prefer sibling. No output schema needed.

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 100% (baseline 3). Description adds usage context: browsing vs reading, and search filter only for index.

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?

Clearly states it reads curated cross-model divergence records, describes content (verbatim answers + axes), and distinguishes from sibling omnarai_council.

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?

Explicitly tells when to omit id (browse index) vs pass id (full record), and advises preferring over omnarai_council when a record exists.

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