Skip to main content
Glama
sweetcornna

free-search-mcp

by sweetcornna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List available search engines

engines
Read-onlyIdempotent

List available search sources grouped by category, letting you pick the right one before searching or researching.

Instructions

List the available sources, grouped by what they index.

Best for:
- Choosing a source deliberately: which one indexes filings, or preprints,
  or Chinese-language pages.
- Checking a name before passing it to `engines=` on `search` / `research`.

Not recommended for:
- Calling on every search: the list is static, so read it once.

Returns (markdown): a `group -> sub-group -> engine` tree, one line of
description per engine. `group="paper"` restricts it to that group.
Returns (json): `{"engines": [...names...], "taxonomy": {...},
"descriptions": {...}}`.

Prefer `category=` over `engines=`. `category="paper"` WIDENS: it routes to
one specialist per sub-group. A dotted sub-group NARROWS: `"paper.biomed"`
queries only the biomedical indexes. Naming engines explicitly turns that
routing off entirely, so reach for it only to force a specific source.

Common mistakes:
- Passing one of these names as `query`: they belong in `engines=`.
- Passing a key-only engine with no key configured; it returns an
  actionable error, not results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupNo
formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • addedInput schema / properties / format
      Added value: +{
+  "default": "markdown",
+  "enum": [
+    "markdown",
+    "json"
+  ],
+  "title": "Format",
+  "type": "string"
+}
    • addedInput schema / properties / group
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "web",
+        "news",
+        "paper",
+        "github",
+        "forum",
+        "image",
+        "dataset",
+        "finance",
+        "software",
+        "security",
+        "reference",
+        "weather",
+        "docs",
+        "gov",
+        "stats",
+        "calendar"
+      ],
+      "type": "string"
+    },
+    {
+      "enum": [
+        "news",
+        "pdf",
+        "github",
+        "paper",
+        "forum",
+        "blog",
+        "image",
+        "dataset",
+        "finance",
+        "software",
+        "security",
+        "reference",
+        "weather",
+        "docs",
+        "gov",
+        "stats",
+        "calendar",
+        "news.world",
+        "paper.index",
+        "paper.preprint",
+        "paper.biomed",
+        "paper.cs",
+        "paper.math",
+        "paper.openaccess",
+        "paper.trial",
+        "dataset.repository",
+        "dataset.ml",
+        "dataset.gov",
+        "finance.filings",
+        "finance.market",
+        "finance.macro",
+        "finance.fx",
+        "finance.entity",
+        "finance.crypto",
+        "software.lifecycle",
+        "software.github",
+        "software.python",
+        "software.node",
+        "software.rust",
+        "software.registry",
+        "software.app",
+        "security.cve",
+        "security.package",
+        "security.exploited",
+        "reference.domain",
+        "docs.web",
+        "docs.rfc",
+        "gov.us",
+        "gov.uk",
+        "stats.indicator",
+        "calendar.holidays",
+        "calendar.clock"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Group"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "type": "string"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "enginesOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds genuinely useful behavioral context: the list is static and should be read once, returns can be markdown or JSON, and key-only engines produce actionable errors. This goes well beyond what annotations convey.

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?

Although long, the description is tightly organized with functional headers, scannable bullet-ish sections, and every sentence adds routing or error-avoidance value. The core purpose is front-loaded, and the detailed guidance is where an agent needs it.

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?

For a read-only list tool with two optional parameters and no output schema, this description is complete: it explains when to use it, what the parameters do, what output format to expect, and likely failure modes. No critical calling information is missing.

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?

Schema coverage is 0%, so the description carries the full burden of explaining parameters. It clarifies `group` values, how dotted sub-groups narrow, how `category=` differs from `engines=`, and what both markdown and JSON output shapes look like. This compensates fully for the schema's lack of parameter descriptions.

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 available sources/engines grouped by what they index, which is specific and immediately distinct from siblings like `search`, `research`, and `fetch`. It names the resource and the organizing principle without ambiguity.

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?

The description gives explicit best-for scenarios, a not-recommended scenario, and detailed routing guidance comparing `category=` vs `engines=` and group/sub-group semantics. It also lists common mistakes, giving an agent both positive and negative selection criteria.

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

Deploy Server

Other Tools