Skip to main content
Glama

omniseek_search

Search curated sources across platforms, deduplicate and rank results by relevance and recency. Use raw mode to drill into one source for full content.

Instructions

Search the curated sources. The default for "best/latest on X". ONE verb, three shapes.

DISPATCH (deterministic): • DEFAULT (raw=False): DEDUP + RANK across sources into ONE list. Cross-source duplicates merge (same paper from arxiv + openalex + … → one entry, the others in metadata.also_in); ordered by a relevance+recency+engagement blend (metadata._rank) you may re-sort — each doc's named signals map (e.g. citations / upvotes / stars, each provenance-stamped) + its date are on the doc. CROSS-LINGUAL + SEMANTIC (default on): also runs VECTOR recall over the local perception-memory index, so a Chinese query surfaces relevant ENGLISH docs (and vice-versa) and paraphrases match with no shared words — fused with the lexical + live results by the SAME transparent ranker (the eye still only retrieves + scores mechanically; you judge). semantic=False forces exact-token lexical-only (an arXiv id / exact title); semantic=True biases toward the vector recall. _meta.index reports {lexical, vector, mode}. Empty query ranks by recency (browse mode). • raw=True + EXACTLY ONE source name (the DRILL idiom, replaces the old omniseek_fetch): fetch that ONE source UNBOUNDED (with wait_s=None the generous single-source backstop; set wait_s to bound it). Reach for it BY NAME on a walled/CDP or slow source (xiaohongshu, zhihu, yipinsanfendi, xiaomuchong, twitter_x, and the explicit_only set): the broad sweep DEADLINE-DROPS these, so only a named drill waits for them — a broad search that comes back without them is NOT evidence they have nothing. full=True returns WHOLE content per doc. A cold walled drill self-warms its cache, so an immediate repeat with the SAME query + SAME limit is sub-second (keep limit identical or the key differs). On an EMPTY / ERRORED drill the result carries _meta.diagnostic (failed-egress evidence + the adapter's source-file path) for the /eye-fix loop; a drill with results carries no _meta (zero noise). • raw=True otherwise (broad buckets): search many sources in parallel → PER-SOURCE buckets, uncollapsed (each source's raw take separately, a tight content preview per doc). limit acts PER SOURCE here. Drill a chosen doc with omniseek_read (whole content), or drop raw for the ranked list.

ROUTING (all shapes): sources=None = all non-explicit_only, deadline-bounded — slow ones drop and are listed in _meta.timed_out. explicit_only sources (browser/CDP + twitter_x) are excluded from the broad sweep → _meta.excluded_count (the size; the full name->reason map is in omniseek_sources) + _meta.excluded_relevant (the query-AWARE subset: walled/slow sources whose facets thematically match THIS query, each with a copy-paste sources=[...] re-run hint). Name them to include their (deeper, login-walled) coverage.

TIME + STALENESS: wait_s = patience budget (None = sensible default; the engine's deadline). staleness ∈ {"fresh","cached_ok","cache_only"} (default cached_ok): "fresh" bypasses the cache (live data); "cache_only" is the fire-then-collect PICKUP half (ranked shape) — with NO live work it reads only what has already SELF-WARMED for the NAMED sources and NEVER re-fires a still-cold walled source (zero extra CDP / account traffic, poll-safe). Fire-then-collect: FIRE omniseek_search(query, sources=[walled...], wait_s=12), then COLLECT omniseek_search(query, sources=[walled...], staleness="cache_only"); use the SAME limit both times (the cache key includes it; a different limit silently misses). _meta.empty = sources not yet warm.

FIRE-THEN-COLLECT IS NOT JUST FOR WALLED SOURCES: it is the BEST way to run an ORDINARY broad search, and it is both faster AND more complete than waiting. A plain broad call blocks ~16s for ~223 docs. Instead FIRE omniseek_search(query, wait_s=3) -> first results in ~3s, then COLLECT omniseek_search(query, staleness="cache_only") ~20s later -> ~296 docs. Measured over 3 quiesced reps (2026-07-25): 5x faster to first result AND ~33% MORE docs than the blocking call. It wins on both axes because sources the deadline would have cut keep running detached and warm the cache with no deadline over them, so the collect reads MORE than the 16s window could ever hold. The cache plateaus by ~+20s (no gain at +35s), so collecting later buys nothing. Same limit both calls. vs the open web: searches only OmniSeek's curated sources; pair with WebSearch for open-web breadth (orthogonal, often use BOTH).

PER-DOC METADATA is LEAN by default: internal ranking/recall telemetry (recall_rrf / freshness_class / relevance_hook / merge_basis / ...) is omitted (~25% of a ranked doc); the SIGNAL stays (_rank, also_in, seen_before / first_seen_at, source-native signals). debug=True keeps the full telemetry (/eye-fix).

Returns (default): {"query", "count", "documents": [...], "_meta": {..., excluded_relevant, "deduped": {in, out}}, routing_hint? (TOP-LEVEL: the strongest excluded vertical/walled matches for THIS query, overlap-ranked, each with its param_hint — name one for its authoritative coverage; present only on a broad sweep with a strong match)}. (raw one-source drill): {"source", "query", "count", "documents": [...], "_meta": {"diagnostic": {...}} # only when empty/errored}. (raw buckets): {"query", "results": {source: [...]}, "total_count", "_meta": {searched, empty, timed_out, errored, excluded_count, excluded_relevant, truncated, progressive:{fast,slow,timed_out}, ...}}. An unknown staleness value is treated as cached_ok and a "note" is added to the return.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNo
fullNo
debugNo
limitNo
queryYes
wait_sNo
sourcesNo
semanticNo
stalenessNocached_ok

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It thoroughly explains deduplication, ranking signals, cache semantics, staleness modes, deadline drops of slow sources, self-warming of cold walled sources, diagnostic payloads on empty/errored drills, and the side-effect-free cache_only pickup. It even covers edge cases like unknown staleness values and the cache key depending on limit, which is exactly the kind of behavioral nuance an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but it earns most of its length by covering three distinct call shapes, routing rules, and return variants. It is front-loaded with the core purpose and uses bolded headers and bullets to create navigable structure. Some measured-performance detail (e.g., ~16s, ~223 docs, +33% counts) is more than strictly necessary, which keeps it from a perfect conciseness score.

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 is remarkably complete. It documents the full return shape for the default ranked result, the raw one-source drill, and raw buckets, including _meta fields like excluded_relevant, deduped, timed_out, and diagnostic. It also covers the fire-then-collect workflow, staleness edge behavior, and relationship to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so every parameter must be explained in the prose. The description covers all nine parameters: query, raw, raw's interaction with sources, limit per source and in cache keys, wait_s as patience budget, staleness values and their semantics, semantic toggle behavior, full for whole content, and debug for telemetry. This fully compensates for the absent schema descriptions.

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?

Opens with a clear verb and resource: 'Search the curated sources. The default for best/latest on X.' It then distinguishes three explicit shapes (dispatch, raw one-source drill, raw buckets), so an agent can tell exactly what the tool does and how the core action branches. It also differentiates itself from siblings by naming omniseek_read for drilling into a chosen doc and omniseek_sources for the source map.

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?

Provides explicit routing: use raw=True with exactly one source for walled/CDP/slow sources, use broad buckets for many sources, and drop raw for the ranked list. It also says when NOT to infer absence of results ('a broad search that comes back without them is NOT evidence they have nothing'), explains fire-then-collect as the preferred pattern, and contrasts with WebSearch for open-web breadth. This gives clear when-to-use and when-not-to-use guidance.

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

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/Battam1111/omniseek'

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