Skip to main content
Glama
bunkerity

BunkerWeb MCP

Official
by bunkerity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configs_list

Read-only

List custom configuration snippets with optional content, filtering by service or type to inspect BunkerWeb config scopes. Use config_get to read a single snippet in full.

Instructions

List custom config snippets (service, type, name), optionally with content. Use config_get to read one snippet in full.

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by type. Custom config type, e.g. http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before, crs-plugins-after
serviceNoFilter by service ID; omit or 'global' to list every scope, global included
with_dataNoInclude each snippet's content; false returns metadata only
with_draftsNoInclude snippets of draft services

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • changedInput schema / properties / service / description
      Previous value: -"Service identifier or global"New value: +"Filter by service ID; omit or 'global' to list every scope, global included"
    • changedInput schema / properties / type / description
      Previous value: -"Configuration type filter"New value: +"Filter by type. Custom config type, e.g. http, server-http, default-server-http, stream, server-stream, modsec, modsec-crs, crs-plugins-before, crs-plugins-after"
    • addedInput schema / properties / with_data / description
      Added value: +"Include each snippet's content; false returns metadata only"
    • addedInput schema / properties / with_drafts / description
      Added value: +"Include snippets of draft services"
  2. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / service / description
      Added value: +"Service identifier or global"
    • addedInput schema / properties / type / description
      Added value: +"Configuration type filter"
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds that content can optionally be included, but it does not disclose further behavioral context such as default draft inclusion or pagination/return behavior.

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?

The description is two tight sentences with zero waste. It front-loads the listing purpose and immediately follows with the key alternative.

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?

For a simple read-only list tool with fully described parameters, the description is largely complete. It explains the return shape at a high level and when to prefer config_get, though it does not mention the with_drafts behavior that may matter to callers.

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 all four parameters are already documented in the schema. The description mentions service, type, and optional content, but adds no syntax, defaults, or filtering details beyond what the schema provides.

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 states a specific verb and resource: list custom config snippets. It names the relevant dimensions (service, type, name) and explicitly distinguishes the tool from config_get for full single-snippet reads.

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?

It gives a clear usage cue by directing users to config_get when reading one snippet in full, implying configs_list is for listing or metadata retrieval. It does not explicitly state when not to use the tool or mention other sibling alternatives, but the context is clear.

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