Skip to main content
Glama
JerryLiu369

agent-web-search

by JerryLiu369
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

web_search

Search the web using multiple providers with a natural-language query. Returns results from successful providers, omitting failures, or an error if all fail.

Instructions

Search the web through multiple providers. Enabled providers: DuckDuckGo web search; Exa web search; Parallel LLM-optimized web search. Use a complete natural-language question. Failed providers are omitted from successful responses. If every enabled provider fails, the call returns a tool error with code all_providers_failed and per-provider diagnostics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA complete natural-language search question.
providersNoOptional subset of the providers enabled at startup.
time_rangeNoOptional time filter: past day, week, month, or year.
max_resultsNoDesired maximum number of results. Providers enforce this natively or as a best-effort prompt constraint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.2
    • removedInput schema / properties / max_keyword
      Removed value: -{
-  "default": 3,
-  "description": "Desired maximum number of distinct search queries or keywords. Providers without an equivalent control ignore it.",
-  "maximum": 10,
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / max_results / description
      Previous value: -"Desired maximum number of results or cited sources. Providers enforce this natively or as a best-effort prompt constraint."New value: +"Desired maximum number of results. Providers enforce this natively or as a best-effort prompt constraint."
    • addedInput schema / properties / query / maxLength
      Added value: +4000
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / providers / items / enum
      Previous value: -[
-  "ark",
-  "ddgs",
-  "exa"
-]New value: +[
+  "ddgs",
+  "exa",
+  "parallel"
+]
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it reveals that failed providers are omitted from successful responses and that total failure surfaces a specific error code all_providers_failed with per-provider diagnostics. It doesn't cover output shape or rate limits, but core operational behavior is disclosed.

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?

Four short sentences, each carrying unique information: purpose, provider list, query format, and failure semantics. It is front-loaded and free of filler.

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?

The description covers purpose, query format, providers, and failure behavior, which is enough for an agent to select and invoke the tool correctly. The absence of an output schema means the return format is not described, but this is a minor gap for a general search tool.

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

Parameters3/5

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

Schema coverage is 100%, so each parameter is already described in the input schema. The description adds a little by naming the providers and re-emphasizing the natural-language query style, but it doesn't materially enrich the meaning of time_range or max_results beyond their schemas.

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 clear verb+resource: 'Search the web through multiple providers,' and enumerates the exact providers (DuckDuckGo, Exa, Parallel). Although there are no sibling tools, the description fully establishes what the tool does and its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context—use a complete natural-language question—and explains provider/error behavior, so an agent knows how to frame calls. No sibling tools exist to contrast with, and no explicit when-not-to-use exclusion is provided, so it stops short of a 5.

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