Skip to main content
Glama

omniseek_sources

Read-only

List available search sources by domain, region, or query token match to route searches to the right source before searching.

Instructions

List all sources: call this to ROUTE before searching.

Tool name: omniseek_sources (your MCP config adds its own prefix; never guess one). Not in your tool list? ToolSearch "omniseek_sources".

A bare call returns the routing vocabulary and the bare inventory, not every source's facets.

Args: domain: only sources whose domains facet has it ("jobs", "papers", ...), with descriptions. query: sources ranked by token overlap with these words (English and Chinese), with descriptions. region: only sources whose regions facet has it ("sg", "ca", "cn", ...). verbose: every source with its full facets and description. field: with a query/domain that picks one source, also return that filter field's known values. check_health: probe every source live (slow) and add a system block.

Returns {count, backend_count, backend_breakdown} plus either the bare orient {source_names, available_domains, available_regions, capabilities, note} or sources: [{name, backend, description, needs_credentials, explicit_only, explicit_only_reason?, param_hint?, stability, access_tier, health, kind?, domains?, regions?, modes?, filters?, coverage?, license?, samples?, as_of_field?}]. backend_count counts distinct upstreams (count over-states coverage). health: ok | down | unmeasured | unverified | unknown | sealed; with check_health, healthy null means not verified, neither working nor failed. A near-miss domain or region returns did_you_mean. More: omniseek docs/TOOLS.md, omniseek_sources.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omniseek_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldNo
queryNo
domainNo
regionNo
verboseNo
check_healthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / field
      Added value: +{
      +  "default": "",
      +  "title": "Field",
      +  "type": "string"
      +}
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, and the description adds genuinely useful behavior beyond it: bare-call vs verbose output differences, check_health being slow, backend_count over-stating coverage, health null meaning 'not verified', and did_you_mean on near-miss domains/regions. The main gap is that it never says what happens on an invalid domain combined with query, or how large the full verbose payload typically is — but the annotated safety bar is met with extra context.

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?

Front-loaded with the routing imperative, then an Args block, then a Returns block — a structure an agent can skim. It carries some avoidable bulk: the tool-name/prefix disclaimer and the trailing 'More: omniseek docs/TOOLS.md, omniseek_sources' pointer add little, and the Returns enumeration is long, though it substitutes for a missing output schema.

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?

There is no output schema, and the description compensates by spelling out both return branches (bare orient object vs per-source records with named fields) and the count/backend_count distinction. For a 6-parameter, zero-coverage, no-annotation-detail tool, nothing an agent needs to call it correctly appears to be missing.

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% across 6 parameters, so the description carries the full burden and does so: every argument is explained with its effect on the response, including the non-obvious interaction that field only applies 'with a query/domain that picks one source'. The verbose and check_health flags are both scoped by cost and result shape, which the schema alone conveys not at all.

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?

States a specific verb and resource ('List all sources') plus its role in the workflow ('call this to ROUTE before searching'), which separates it from the sibling search tool without ambiguity. An agent can tell immediately that this is the inventory/routing step rather than a retrieval step.

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?

Gives explicit when-to-use ('ROUTE before searching') and per-argument selection guidance: domain for facet-restricted sources with descriptions, query for token-overlap ranking, region for regional subsets, verbose for full facets, field for enumerating a filter's values. It also warns that a bare call returns only routing vocabulary and bare inventory, which tells the agent when the default is insufficient.

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