Skip to main content
Glama
aidvizhhub

camoufox-research

by aidvizhhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Веб-поиск

web_search
Read-onlyIdempotent

Perform a single-query web search for facts, news, or exact URLs via DuckDuckGo. Returns titles, links, and optional snippets with pagination and proxy support.

Instructions

Когда: БЫСТРЫЙ ОТВЕТ — один запрос, факт, новость, точный URL. Что: номера, заголовки и URL из DuckDuckGo (анти-детект браузер), кэш на сутки; include_snippets — сниппет под URL, pages>1 — пагинация. engines — явный список движков для диагностики (["brave"], ["ddg_html","bing"]), пусто — цепочка из env CAMOUFOX_SEARCH_ENGINES; transport — "auto"/"http"/"browser" (HTTP-фолбэк быстрее, браузер нужен JS/consent-движкам); proxy — разовый прокси на этот вызов ('host:port', 'user:pass@host:port', 'socks5://host:port'); без них поведение прежнее. Не когда: нужно 10+ разных сайтов → research (сейчас); научные статьи → paper_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pagesNo
proxyNo
queryYes
enginesNo
transportNoauto
max_resultsNo
include_snippetsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.21.1
    • addedInput schema / properties / engines
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Engines"
+}
    • addedInput schema / properties / proxy
      Added value: +{
+  "default": "",
+  "title": "Proxy",
+  "type": "string"
+}
    • addedInput schema / properties / transport
      Added value: +{
+  "default": "auto",
+  "enum": [
+    "auto",
+    "http",
+    "browser"
+  ],
+  "title": "Transport",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive/open-world, and the description adds real context beyond them: anti-detect browser backend, 24h cache, engines defaulting to the CAMOUFOX_SEARCH_ENGINES chain, HTTP fallback being faster, and browser transport required for JS/consent engines.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with Когда/Что/Не когда and no filler sentences, but the 'Что' block is a dense run-on with nested parentheticals and example values that takes effort to parse.

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?

With an output schema present, return values need not be explained, and annotations cover safety. The description supplies usage routing, backend/cache behavior, and most parameter meanings; only max_results semantics remain unaddressed.

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?

Schema coverage is 0%, so the description must carry the burden — and it explains include_snippets, pages, engines (with example values and the empty-chain default), transport modes, and per-call proxy formats. max_results is never mentioned, leaving one of seven parameters undocumented.

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 specific verb+resource (быстрый веб-поиск через DuckDuckGo) and what it returns (номера, заголовки, URL). It explicitly distinguishes itself from siblings by naming 'research' and 'paper_search' as different tools.

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?

Uses an explicit Когда / Не когда structure: one query, fact, news, exact URL is the target; 10+ different sites → research, scientific articles → paper_search. The routing decision is fully specified with named alternatives.

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