Skip to main content
Glama

engines

Read-onlyIdempotent

Retrieve the list of search provider names that can be specified when customizing the search source. Enables building UIs for provider selection before searching.

Instructions

List engine names accepted by the engines= parameter of search / research.

Best for:
- Discovering what's installable before passing a non-default engine.
- Building user-facing UIs that let humans pick engines.

Not recommended for:
- Calling on every search — the list is static; cache it.

Returns:
- A list of engine name strings (e.g. ["duckduckgo", "mojeek",
  "googlenews", "startpage", "brave", "bing", "baidu"]).

Common mistakes:
- Passing one of these names as a query to `search` — they go in the
  `engines=` argument, not `query`.

Defaults: duckduckgo + mojeek + googlenews (all reliable, no captchas;
          googlenews is an RSS index with structured publish dates).
Opt-in:   startpage (browser-rendered, slower), brave (PoW captcha after a
          few calls), bing (UA-gated), baidu (results wrapped in
          baidu.com/link redirects).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate read-only and idempotent nature. Description adds valuable context: list is static, recommends caching, and details engine characteristics (captchas, speed, redirects) that affect behavior.

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?

Structured with sections, front-loaded purpose, minimal waste. Every sentence serves a purpose, includes examples and caveats without being verbose.

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?

Despite simplicity, covers list content, return format, common mistakes, caching strategy, and engine-specific behaviors. Output schema exists, so return values are known. Complete for the tool's complexity.

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?

No parameters (0 params, schema coverage 100%). Description doesn't need to add parameter details; baseline 4 applies.

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?

Description explicitly states it lists engine names for the `engines=` parameter of `search`/`research`. Clearly distinguishes from siblings like `search` and `research` by its specific purpose.

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 best-for and not-recommended-for scenarios, including caching advice and common mistakes. Offers explicit guidance on when to use and when not to, with detailed notes on defaults and opt-in engines.

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/sweetcornna/free-search-mcp'

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