BunkerWeb MCP

Official

Overview Schema Source Related Servers Discussions Admin

search_bunkerweb_docs

Read-only

Search BunkerWeb documentation by meaning in any language to answer how-to and setting questions. Returns relevant sections with title, URL, category, relevance score, and content.

Instructions

Search the official BunkerWeb documentation by meaning, in any language. Returns up to limit sections with title, URL, category, relevance and content, one per document. Use it for how-to and setting questions; use the API tools to read live state. Lower min_score if nothing matches.

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": "search_bunkerweb_docs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return, 1 to 50
`query`	Yes	Question or topic in natural language, any language
`category`	No	Optional docs section filter, e.g. api, plugins, features
`min_score`	No	Relevance threshold from 0 to 1; lower it when nothing matches
`max_content_length`	No	Characters of content per result; 0 returns full sections

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.6.0Oct 23, 2026

addedInput schema / properties / category / description

Added value: +"Optional docs section filter, e.g. api, plugins, features"

addedInput schema / properties / limit / description

Added value: +"Maximum results to return, 1 to 50"

addedInput schema / properties / max_content_length / description

Added value: +"Characters of content per result; 0 returns full sections"

addedInput schema / properties / min_score / description

Added value: +"Relevance threshold from 0 to 1; lower it when nothing matches"

addedInput schema / properties / query / description

Added value: +"Question or topic in natural language, any language"

First observedv0.1.0Oct 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds non-obvious behavior: results are one section per document with title, URL, category, relevance and content, and it discloses the recovery tactic of lowering min_score when nothing matches.

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?

Three short sentences, front-loaded with the core action and retrieval mode, then routing guidance, then tuning. The phrase 'one per document' is slightly ambiguous filler but nothing is padded.

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 and full parameter descriptions, the description need not explain return payloads, and it still offers a useful summary of shape. The only remaining gap is guidance on ranking behavior and whether the index reflects the deployed version, which an agent might reasonably want.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description reinforces that the query is natural-language and language-agnostic and that limit bounds result sections, but the min_score tuning advice largely duplicates the schema's own wording ('lower it when nothing matches') and category is not elaborated at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the official BunkerWeb documentation') plus the retrieval method ('by meaning, in any language'), which is more than a restated name. It does not name a specific sibling, referring only to 'the API tools' collectively, so differentiation is directional rather than precise.

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

Usage Guidelines4/5

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

Gives an explicit use case ('how-to and setting questions') and an explicit exclusion that routes live-state questions to the API tools. The alternative is described by category rather than by naming a sibling, so the agent must infer which of the ~35 API tools applies.

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