Skip to main content
Glama
bunkerity

BunkerWeb MCP

Official
by bunkerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

config_update

Destructive

Edit, rename, or move a single configuration snippet while keeping omitted fields unchanged; changes save to the database for later scheduler application, not immediate live confirmation.

Instructions

Edit, rename or move one snippet from text; omitted fields keep their value. Use config_upload_update to send a file. Saved to the database; the scheduler applies it later; this tool cannot confirm it is live.

Input Schema

NameRequiredDescriptionDefault
dataNoNew snippet content; omit to keep
nameYesSnippet name: letters, digits, _ or -, no extension
typeYesCustom config type, e.g. http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before, crs-plugins-after
serviceNoService ID that owns the snippet; omit or 'global' for global
is_draftNoSet the draft flag; omit to keep
new_nameNoRename the snippet; omit to keep
new_typeNoChange the type; omit to keep
new_serviceNoMove to this service; omit to keep

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.6.0
    • addedInput schema / properties / data / description
      Added value: +"New snippet content; omit to keep"
    • addedInput schema / properties / is_draft / description
      Added value: +"Set the draft flag; omit to keep"
    • changedInput schema / properties / name / description
      Previous value: -"Configuration name"New value: +"Snippet name: letters, digits, _ or -, no extension"
    • addedInput schema / properties / new_name / description
      Added value: +"Rename the snippet; omit to keep"
    • addedInput schema / properties / new_service / description
      Added value: +"Move to this service; omit to keep"
    • addedInput schema / properties / new_type / description
      Added value: +"Change the type; omit to keep"
    • changedInput schema / properties / service / description
      Previous value: -"Service identifier or global"New value: +"Service ID that owns the snippet; omit or 'global' for global"
    • changedInput schema / properties / type / description
      Previous value: -"Configuration type"New value: +"Custom config type, e.g. http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before, crs-plugins-after"
  2. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / name / description
      Added value: +"Configuration name"
    • addedInput schema / properties / service / description
      Added value: +"Service identifier or global"
    • addedInput schema / properties / type / description
      Added value: +"Configuration type"
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses the crucial asynchronous behavior: the change is saved to the database and the scheduler applies it later, so the tool cannot confirm the change is live. That is real value an agent cannot infer from the structured fields. It stops short of stating reversibility or permission requirements.

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 tight sentences with zero waste: operation and merge semantics first, sibling routing second. The important asynchronous caveat is packed into the same space without padding.

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 a fully described 8-parameter schema, no output schema, and destructive annotations, the description supplies exactly the missing pieces: the patch contract, the sibling alternative, and the eventual-consistency caveat. Nothing an agent needs to call this correctly is absent.

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 every one of the 8 parameters is already documented, including the per-param 'omit to keep' note. The description's merge-semantics sentence restates that contract rather than adding new meaning, so the baseline of 3 applies.

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 set (edit, rename, move) against a specific resource (one snippet, inline text) and explicitly separates itself from the file-based sibling config_upload_update. An agent can identify the operation and its scope without opening the schema.

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?

Names the alternative for file uploads ('Use config_upload_update to send a file') and states the patch-style contract that omitted fields keep their value. It does not distinguish config_update from config_create or state any precondition around draft vs. live snippets, but the key sibling routing is explicit.

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