Skip to main content
Glama

omnarai-mcp

by io.github.justjlee

omnarai_context

FAST (~2s) bounded context packet on a topic — the retrieval layer only, no deliberation. Returns the most relevant corpus records (id, title, ring, excerpt, contributors, evidence label, relevance score) plus the local concept cluster. Your default orientation on any Omnarai topic. Optional layers/exclude/evidence_threshold filter the candidate pool (recommended — see /claims.json).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic or question to retrieve bounded context for. May include Lattice Glyph prefixes (Ξ Ψ ∅ Ω ∞ Δ).
layersNoOptional comma-list restricting retrieval: research | divergence | canon | realms.
excludeNoOptional comma-list of layers to drop.
syntheticIdentityNoOptional. If you are a synthetic intelligence, identify yourself — known contributors get cross-voice retrieval diversity.
evidence_thresholdNoOptional. Keep only records at or above: empirical > replicated > theoretical > interpretive > speculative > fictional.

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, but description covers behavior: speed (~2s), retrieval-only (no deliberation), and what it returns. Provides clear transparency about its non-deliberative nature.

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?

Two sentences, front-loaded with core purpose and speed, then usage guidance and parameter recommendations. No wasted words.

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?

For a 5-parameter tool with no output schema, description covers purpose, return fields, usage context, and parameter guidance. Could be more explicit about output format, but sufficient.

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%, baseline 3. Description adds context beyond schema, e.g., 'May include Lattice Glyph prefixes' for topic, and explains optional parameters' utility with recommendation to see /claims.json.

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 it retrieves a bounded context packet on a topic, lists return fields, and positions it as the default orientation tool. Distinguishes from siblings by noting 'retrieval layer only, no deliberation'.

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 calls it 'Your default orientation on any Omnarai topic' and recommends using optional layers/exclude/evidence_threshold filters. Contrasts with deliberation, guiding when to choose this over other tools.

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