Skip to main content
Glama

novada_search

Read-onlyIdempotent

Search the web using multiple engines (Google, Bing, DuckDuckGo, Yahoo, Yandex) to find relevant results including titles, URLs, and snippets. Supports options for time range, domains, and auto-extraction.

Instructions

Search the web via 5 engines (Google, Bing, DuckDuckGo, Yahoo, Yandex). Returns titles, URLs, snippets — reranked by relevance. For complex questions needing multiple sources, use novada_research instead (it's faster and more thorough).

Use for: Current events, finding URLs, fact lookup, competitive research. Set enrich_top=true to auto-extract the #1 result. Not for: Reading a known URL (novada_extract), multi-source report (novada_research). Tip: engine='duckduckgo' is 3x faster than Google and works for most queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
engineYesSearch engine to use. 'google': best general relevance (default). 'bing': good for news and local. 'duckduckgo': privacy-focused. 'yahoo': broad index. 'yandex': Russian/Eastern European content.google
numYes
countryYes
languageYes
time_rangeNoLimit results to a time window. 'day'=last 24h, 'week'=last 7 days, 'month'=last 30 days, 'year'=last 12 months.
start_dateNoISO date YYYY-MM-DD. Return results published on or after this date.
end_dateNoISO date YYYY-MM-DD. Return results published on or before this date.
include_domainsNoOnly return results from these domains. E.g. ['github.com', 'arxiv.org']. Max 10.
exclude_domainsNoExclude results from these domains. E.g. ['reddit.com', 'quora.com']. Max 10.
formatYesOutput format. 'markdown': human-readable (default). 'json': structured object for programmatic agent use.markdown
enrich_topNoAuto-extract full content from the top result. Shorthand for extract_options.top_n=1. Adds ~2-4s latency. Default: false.
extract_optionsNoWhen provided, automatically extracts content from the top top_n search result URLs and appends it to each result. Eliminates a separate novada_extract call. Note: adds latency proportional to top_n * extract_latency. Use top_n=1-3 for most queries.
Behavior4/5

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

Annotations indicate read-only, idempotent, open-world. Description adds behavioral details: reranking, optional enrichment with latency cost, engine speed differences. No contradiction with annotations.

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?

Extremely concise: main description plus bullet points for use/not-for/tip. Every sentence provides useful guidance without redundancy. Front-loaded with key facts.

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?

Covers tool purpose, parameter highlights, use vs. alternatives. No output schema, but return content is described. Could mention result count limits, but overall sufficient for an agent.

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 description coverage is 69% (high). Description adds value by clarifying enrich_top as shorthand for extract_options.top_n=1 and noting DuckDuckGo speed. Guide helps parameter selection beyond 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 clearly states it searches the web via 5 engines, returns titles/URLs/snippets reranked by relevance, and distinguishes itself from sibling tools like novada_research and novada_extract. It provides specific use cases and exclusions.

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 lists 'Use for' (current events, fact lookup, etc.) and 'Not for' (reading a URL, multi-source report) with alternative tools named. Also includes a tip about engine speed for DuckDuckGo.

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

Install Server

Other Tools

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/NovadaLabs/novada-mcp'

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