Skip to main content
Glama

Web Search

infobroker_search_web
Read-onlyIdempotent

Search the web, encyclopedia, and code sources with one query. Enable autocomplete, query expansion, or deep-read research for comprehensive results.

Instructions

Search the web, encyclopedia, academic, and code sources through one interface with automatic provider selection and a fallback chain. Use when you need broad or batched search, query autocomplete (suggest), query expansion (expand), ranked passages from the top pages (deep), or a multi-variant research compile that deep-reads each variant (research). Do NOT use for a URL you already have (use infobroker_fetch_page), for high-stakes claim verification (use infobroker_verify_claims), for stored-report recall (use infobroker_manage_kb search), or for academic citations (use infobroker_get_citations). Caches results in the local knowledge base, enforces per-provider rate limits, and needs no API key for the free providers. Returns a JSON envelope prefixed [OK] or [ERROR] with status, provider, results, and meta.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deepNoRead the top results and return each page's ranked passages against the query
pageNoResults page number (default 1)
queryYesSearch query: a single string, or up to five strings searched in parallel
expandNoReturn query-expansion strings instead of search results
regionNoISO region/country code (e.g. 'us-en', 'DE')
suggestNoReturn query-autocomplete strings instead of results (default false)
priorityNoRoute by intent: speed, quality, privacy, or free_only
providerNoProvider slug (auto-select if omitted)
researchNoResearch compile: fan out to derived query variants and deep-read each, returning passages grouped by variant (default off)
time_rangeNoRestrict results to day, week, month, or year
max_resultsNoNumber of results to return (1-30, default 8)
safe_searchNoSafe-search filtering: on, off, or strict (default on)on
content_typeNoSource kind to search: docs, issue, changelog, blog, spec, or all (default all)all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A5/5.0
Behavior5/5

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

Discloses caching, rate-limit enforcement, no-API-key behavior, and the [OK]/[ERROR] JSON envelope. These details align with the readOnlyHint, openWorldHint, idempotentHint, and destructiveHint 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?

The description is compact but information-dense, using clear 'Use when' and 'Do NOT use' sections without redundant 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?

Even without an output schema, it names the return envelope and its top-level fields, describes side effects, and gives enough context for an agent to choose and invoke the tool correctly.

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?

All 13 parameters are described, with defaults and enums explicitly covered; the query parameter's string-or-array(max 5) behavior is explained, and mode flags like deep/expand/suggest/research are clarified.

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 the tool searches web, encyclopedia, academic, and code sources through one interface, with a clear 'Use when...' list covering broad/batched search and modes. It also names sibling tools for disambiguation.

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 describes when to use it and when not to, pointing to infobroker_fetch_page, verify_claims, manage_kb, and get_citations for exclusions.

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