Skip to main content
Glama
wojtekkura

cf-mcp

by wojtekkura
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

cf_get_bot_management_config

Retrieve Bot Management configuration including fight mode, JavaScript detection, and AI bot protection settings for a Cloudflare zone.

Instructions

Get the current Bot Management configuration for a zone.

Args:
    zone_id: 32-char Cloudflare zone ID.

Calls: GET /zones/{zone_id}/bot_management.

Returns: envelope with `data` = the full BM config dict, including:
    - fight_mode (bool)
    - using_latest_model (bool)
    - enable_js (bool)
    - sbfm_definitely_automated (str — block/allow/managed)
    - sbfm_likely_automated (str)
    - sbfm_verified_bots (str)
    - sbfm_static_resource_protection (bool)
    - optimize_wordpress (bool)
    - suppress_session_score (bool)
    - auto_update_model (bool)
    - ai_bots_protection (str — block/disabled)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zone_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses the HTTP GET method, URL pattern, and details the full return structure with all fields and types (e.g., bool, string). This provides excellent transparency into the tool's read-only behavior and output.

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?

The description is well-structured with clear sections for args, HTTP call, and returns. It's slightly lengthy due to the full list of return fields, but every sentence provides value. It is front-loaded with the main purpose.

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 one parameter and the presence of an output schema (though not shown), the description provides the complete return structure. It covers all necessary details for an agent to correctly invoke the tool and understand the response.

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

Parameters5/5

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

The single parameter zone_id is described as '32-char Cloudflare zone ID', adding meaningful context beyond the schema's type 'string'. With 0% schema description coverage, the description fully compensates by specifying the format and purpose.

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 clearly states the tool retrieves the current Bot Management configuration for a zone, with a specific verb 'Get' and resource 'Bot Management configuration'. It distinguishes itself from siblings like cf_list_super_bot_fight_mode_config, which lists configs, by focusing on a single zone's full config.

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?

The description implies usage when needing a specific zone's bot management config, but lacks explicit guidance on when not to use it or direct comparison to sibling tools like cf_list_super_bot_fight_mode_config. The context is clear but exclusions are absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wojtekkura/cf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server