4get MCP Server

fourget_news_search

Read-onlyIdempotent

Retrieve news articles from the 4get meta search engine, including titles, URLs, descriptions, publication dates, and thumbnails. Paginate results using an optional token.

Instructions

Search for news articles using the 4get meta search engine. Returns recent news with titles, URLs, descriptions, publication dates, and thumbnails. Supports pagination via the 'npt' token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fourget_news_search"
  }
}

Input Schema

Name	Required	Description
`query`	Yes
`engine`	No	Optional search engine override (maps to 4get "scraper" query parameter).
`page_token`	No
`extra_params`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.2May 4, 2026

removedInput schema / $defs

Removed value: -{
-  "SearchEngine": {
-    "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
-    "enum": [
-      "ddg",
-      "brave",
-      "mullvad_brave",
-      "yandex",
-      "google",
-      "google_cse",
-      "mullvad_google",
-      "startpage",
-      "qwant",
-      "ghostery",
-      "yep",
-      "greppr",
-      "crowdview",
-      "mwmbl",
-      "mojeek",
-      "baidu",
-      "coccoc",
-      "solofield",
-      "marginalia",
-      "wiby",
-      "curlie"
-    ],
-    "type": "string"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / engine / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/SearchEngine"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+    "enum": [
+      "ddg",
+      "brave",
+      "mullvad_brave",
+      "yandex",
+      "google",
+      "google_cse",
+      "mullvad_google",
+      "startpage",
+      "qwant",
+      "ghostery",
+      "yep",
+      "greppr",
+      "crowdview",
+      "mwmbl",
+      "mojeek",
+      "baidu",
+      "coccoc",
+      "solofield",
+      "marginalia",
+      "wiby",
+      "curlie"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / $defs

Added value: +{
+  "SearchEngine": {
+    "description": "Enumeration of supported 4get scrapers with human-friendly labels.",
+    "enum": [
+      "ddg",
+      "brave",
+      "mullvad_brave",
+      "yandex",
+      "google",
+      "google_cse",
+      "mullvad_google",
+      "startpage",
+      "qwant",
+      "ghostery",
+      "yep",
+      "greppr",
+      "crowdview",
+      "mwmbl",
+      "mojeek",
+      "baidu",
+      "coccoc",
+      "solofield",
+      "marginalia",
+      "wiby",
+      "curlie"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / engine

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/SearchEngine"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional search engine override (maps to 4get \"scraper\" query parameter)."
+}

First observedSep 26, 2025

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly and idempotent. Description adds return field list and pagination mechanism ('npt' token), providing useful behavioral context beyond 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?

Two concise sentences; no wasted words. Front-loaded with purpose and includes key details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides core purpose and pagination info but omits details on engine and extra_params. Output schema exists but not visible; still, description could be more complete given low parameter documentation.

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

Parameters2/5

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

Schema description coverage is low (25%). Description mentions page_token indirectly via 'npt' but does not explain engine, extra_params, or their purpose. Fails to compensate for low coverage.

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 clearly states 'Search for news articles' using a specific engine, and lists returned fields. Name and description distinguish from sibling tools (image/web search).

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

Usage Guidelines3/5

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

No explicit guidance on when to use vs siblings. While the name implies news context, the description does not state usage conditions or alternatives.

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

Deploy Server