Skip to main content
Glama
ymylive

free-search-mcp

by ymylive
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

engines

Read-onlyIdempotent

List accepted engine names for the search tool's engines= parameter to discover available options before making a search request.

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",
  "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 + startpage (all reliable, no captchas).
Opt-in:   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

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnly and idempotent, so the description adds value by listing default engines and opt-in behaviors, though it does not mention future updates or static nature beyond caching advice.

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?

Highly structured with clear sections (best-for, not recommended, returns, mistakes, defaults/opt-ins), no extraneous content.

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?

Given zero parameters and the output schema, the description is fully complete, covering usage, typical values, and integration with sibling tools.

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?

With no parameters, the description explains the output's purpose and content (list of strings), adding meaning beyond the empty 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 the tool lists engine names for the engines= parameter, distinguishing it from sibling tools like search and research.

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 explicit best-for and not-recommended-for scenarios, including caching advice and common mistakes, making when-to-use unambiguous.

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

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